Well, there may already be a solution Julien. Read the thread of this email chain more closely for what that is. I am trying it now ;-).
--- Todd Thiessen > -----Original Message----- > From: Julien Stern [mailto:[email protected]] > Sent: Thursday, March 05, 2009 2:02 PM > To: Maven Users List > Subject: Re: release:prepare cannot find artifacts > > Todd Thiessen wrote: > > hehe. Thats where this entire conversation started. Doing > an "install" during a prepare has be commented as a bad idea. > I was confused by this statement and asked for clarification. > > Sorry, I only had the end of the conversation in front of my eyes... > Anyway, I concur that the "release" behavior should be > improved to avoid this and to take the "just created" > artifact. This cause us a lot of trouble especially with > non-jar artifacts and packaging... > > > > --- > > Todd Thiessen > > > > > >> -----Original Message----- > >> From: Julien Stern [mailto:[email protected]] > >> Sent: Thursday, March 05, 2009 1:51 PM > >> To: Maven Users List > >> Subject: Re: release:prepare cannot find artifacts > >> > >> Jörg Schaible wrote: > >>> Todd Thiessen wrote at Donnerstag, 5. März 2009 19:17: > >>> > >>>> Ok. This is not what is recommended in the definitive > >> guide though. > >>>> It is very clear in the optimzing POM section that > >> ${project.version} > >>>> should be used when referencing sibling projects. > >>> Well, actually this worked with older versions of the > >> release plugin > >>> ;-) > >> If I understand your issue all right, I believe you can > solve it by > >> passing -DpreparationGoals="clean install verify" > >> (instead of the default "clean verify" to mvn release:prepare. > >> > >> We manage to keep on using ${project.version} like this. > >> > >> Cheers, > >> > >> -- > >> Julien > >> > >> > --------------------------------------------------------------------- > >> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
