Dennis Lundberg wrote:
Which of these do we intend to fix and which can be bumped to the next version?
Personally, I don't see much value in having an issue scheduled for some release when nobody has actually time/interest to work on it, thereby blocking a release. Go for as much as you can and release it, flushing the improvements that have been made to the users.
Looking at the dependencies and prerequisites for Release Manager and Release Plugin, the manager uses Maven 2.0.8 dependencies, but the plugin uses 2.0.6 dependencies which also match its Maven prerequisite. Could this be a problem and should we align these two so that the plugin uses/requires Maven 2.0.8?
It seems the 2.0.8 deps are only required for encoding support, i.e. the release manager still compiles&runs with Maven 2.0.6. On the other hand, Maven 2.0.6 is pretty old, not sure how many users would actually get excluded by bumping the plugin prerequisite to 2.0.8 as well.
Finally, can we *please* make this a 2.0 release and not yet another beta?
+1 Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
