Joakim Erdfelt wrote: > I still use 2.0.5 daily at the office. > I do have 2.0.7 and 2.0.8 installed too, but there's some bad > juju (re: > bugs) starting in 2.0.6+ WRT corporate repositories, wagon lightweight > http, non-projects (archetype, install-file, deploy-file, eclipse, > etc...) and also plugin resolution. So we are stuck on 2.0.5 for the > time being. > > John Casey has recently closed many of the bugs that we are > having with > 2.0.6+, but there hasn't been a release of 2.0.x yet with > those fixes in it. > I've been using a build from the maven-2.0.x branch for a week or so > that seems to address many of the issues, but haven't fully > fleshed out > the use cases yet.
Same here, but it is getting promising (http://jira.codehaus.org/browse/MNG-3259#action_124708). Although we use fixed plugin versions, we start to miss added functionality. Nothing really critical yet, but it gets annoying. And there are already quite some plugin's that latest versions cannot be used in M205 anymore: - maven-changes-plugin - maven-dependency-plugin - maven-jar-plugin - maven-javadoc-plugin - maven-war-plugin Additionally I would really appreciate if the plugin documentation would also document the minimal Maven version. Normally you simply notice when the plugin breaks your build claiming it needs a newer version. This is especially nasty if the plugin is normally only used during the release ... - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
