Yes, that's the idea. Bryan Keech <bryan.keech.h...@statefarm.com> wrote:
So how about this: I have Hudson CI build run the release to automatically update the version each time. Would that work? -----Original Message----- From: Manfred Moser [mailto:manf...@mosabuam.com] Sent: Thursday, March 31, 2011 11:02 PM To: Maven Users List Cc: Bryan Keech Subject: Re: One Agile automated CI build You say .. deployment again of that same version(but with changes) I say.. don't do that. If it has changes it is NOT the same version. Just use release plugin or whatever to automate changing the version. Maven is going to make it hard for you to do the wrong thing. Just do the right thing and change the version.. manfred > Let me see if I understood... you don't want the previous versions that > were > in artifactory to be lost when you upload an artifact with changes but > with > the same version configured in pom? > > If that's what you're looking for, I dont think you would have other > choice > but to change the version of your artifact before build. > > On! Fri, Apr 1, 2011 at 12:02 AM, Bryan Keech > <bryan.keech.h...@statefarm.com >> wrote: > >> In my case we are building J2EE apps. >> >> Maybe me explaining what I am after would help. :) >> >> I would like this flow to happen: >> >> - Developer commits >> - CI build is done on Hudson >> - artifacts are stored in our remote repository (artifactory) >> - artifacts can then be deployed to a jvm >> >> Currently if we have a version already deployed to artifactory and we do >> a >> deployment again of that same version(but with changes), it overwrites >> what >> is in artifactory. >> >> I guess I am looking for a way for each build to be available in >> artifactory. >> >> Thanks >> Bryan >> >> -----Original Message----- >> From: Tim Pizey [mailto:tim.pi...@gmail.com] >> Sent: Wednesday, March 30, 2011 2:02 PM >> To: Maven Users List >> Cc: Bryan Keech >> Subject: Re: One Agile automated CI build >> >> Hi Brian, >> >> I think we have a very simple system, and we do not use artefactory. ! >> >> I hope I am right in thinkin g you are deploying a war. >> >> We use jenkins with the following command: >> >> mvn clean install deploy tomcat:deploy -Pstaging >> >> this stores artifacts, be they snapshot or release, to the repository >> and deploys to staging. >> >> hope this makes sense >> >> cheers >> Tim >> >> On 30 March 2011 19:24, Bryan Keech wrote: >> > Can anyone give details on how they have done this? I am running into >> road blocks. >> > >> > If I leave the version as a non-snapshot, then Hudson deploys to >> artifactory and overwrites the same version in the repo. I have toyed >> with >> using install:install-file goal in the install phase. >> > >> > Thanks, >> > Bryan >> -- >> Tim Pizey - http://pizey.net/~timp >> Centre for Genomics and Global Health - http://cggh.org >> >_____________________________________________ To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
