:( bummer... I think there should be a notice somewhere in this plugin site. I think this plugin is one of the best maven seller. I have a big multi-module project and was counting on this feature when performing a release (fault's on me for not trying first, I will try later today if possible, just to be sure).
On Tuesday 09 December 2008 11:10:23 John Stoneham wrote: > On Tue, Dec 9, 2008 at 9:40 AM, Thomas Jackson > > <[EMAIL PROTECTED]> wrote: > > I expect the release plugin to change the version number in the > > dependency section for snapshots when it asks me to resolve the > > dependencies and I answer yes. Let me try to give you a concrete > > example..... > > Unfortunately - and everyone who learns the release plugin ends up > having to learn this the hard way - a large part of the 'resolve these > dependencies' bit does not work so well. Browsing the release plugin's > open defects will convince you of this fact. I hope to spend some time > next year trying to help out with some of this myself, because it's > frustrating. > > The release plugin will happily keep snapshot dependencies up to date, > assuming they are dependencies on artifacts you're -also releasing > within the same lifecycle-. Otherwise - it is best to resolve them by > hand for now. > > (My usual procedure is to run release:prepare, and if it finds any > SNAPSHOT dependencies left unresolved, Ctrl-C, mvn release:clean, > resolve them by hand, repeat as necessary. You also need to check the > file for the word SNAPSHOT anyway, because there's a known problem > where it does not detect SNAPSHOT plugin-level dependencies.) > > - John > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- David Ojeda
