cheers Trent, thats very useful. I need to start investigating how to do a release using CVS now...
On 11/11/05, Trent Rosenbaum <[EMAIL PROTECTED]> wrote: > Hi there, > > The deploy stage of the maven build life cycle is focused on the > delivery of the artifact into a > repository for other users, so in one sense you are going in the right > direction. The maven-release plugin is focused on the preparation and > the creation/delivery of a more offical release of a project artifact. > By using SNAPSHOT designator you are indecating that your project is > in a state of development. The time stamps allow others to understand > which is the latest instance of your artifact. > > Below you have you mentioned that you would be happy with your > artifact being called common-1.0.jar. You could modify your pom.xml > and remove the SNAPSHOT designator and then use deploy, I beleive this > would send the correctly named artifact to the remote repository. I > would not do this in a company environment, instead I would use the > maven-release plugin when version 1.0 is ready to be released. This > would allow me to update the SCM and then others in my company could > always recreate it and investigate any potential issues. The plugin > would then modify the pom.xml to allow me to work on the next version, > (for example 2.0-SNAPSHOT). > > I hope I have not gone over board and this helps. > > Trent > > > On 10/11/05, Pete <[EMAIL PROTECTED]> wrote: > > I have a common jar artifact that I have built and now want to deploy > > to my company's remote repository, so I tried :- > > > > mvn deploy > > > > and saw that I needed to add :- > > > > <distributionManagement> > > <snapshotRepository> > > <id>remote_repository</id> > > <name>remote_repository Repository</name> > > <url>file:///server/remote/.m2/repository</url> > > </snapshotRepository> > > </distributionManagement> > > > > to the parent pom.xml . ok > > > > All works fine but then I look in the remote repository I see > > > > \1.0-SNAPSHOT > > Common-1.0-20051110.221828-1.jar > > Common-1.0-20051110.221828-1.pom > > > > with timestamps on the jar names etc. > > > > I want to share this jar as either > > 1.0-SNAPSHOT or > > 1.0 > > > > Am I taking the wrong approach ? What is deploy for ? > > Should I be using mvn release ? > > I thought I could get away with the more simplistic deploy (to remote repo) > > ? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
