On 20/01/2010, at 6:56 AM, Dennis Lundberg wrote: > Okay, we're now down to 0 issues left in JIRA for a 2.0 release. > > Does anybody have anything more they want to add before I start the > release process?
I fixed up a test failure on Windows. I got bitten by this again this week, so I'd like us to put to bed MRELEASE-3 / MRELEASE-240 - the existence of @requiresDependencyResolution on prepare - once and for all. As I understand it, in Maven 3.x this will go away as there is a new tag that will allow interrogating the models, without doing all the resolution. However, it's some time before the plugin can move up to requiring that new tag. As the resolution is only needed for the release poms which are off by default, in hindsight I don't think we should have added it. Would the following be workable? 1) Remove the resolution tag from prepare 2) Add a new mojo :prepare-full, that extends prepare and adds the resolution tag 3) Add a warning in :prepare if you use generateReleasePoms = true without calling prepare-full This would allow us to keep both issues closed (MRELEASE-3 is very high on the vote list). Alternatively, we could add the mojo the other way around, giving less disruption to the current behaviour while making it possible to prepare without the resolution. It just seems back to front though :) What are your thoughts? - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
