2009/4/21 Benjamin Bentmann <[email protected]>: > Stephen Connolly wrote: > >> Paul Gier and I have been working on the versions-maven-plugin. we've made >> quite a few >> changes since 1.0-alpha-2 and I would like to cut another alpha release. > > +0, not using it. Notes: > > "mvn dependency:analyze" reports some unused but declared dependencies. > Among others plexus-component-api. This artifact conflicts with > plexus-container-default as used by Maven and should not be there at all. > Over in Apache land, there's already an Enforcer rule to ban this > dependency, I just added the same for the mojo-parent. >
fixed (when will you call a vote for new mojo parent with this enforcer rule?) > The POM snippet at the end of the usage.html doesn't include a <version> > element for the plugin declaration. fixed > > The mojo parameter "settings" should better be marked as @readonly. fixed > >> Note: while this vote is on-going we will be continuing to add / fix >> integration tests, but I don't see that this should prevent the release as >> we will not be changing the source, only the integration tests. > > OK, so I assume this matches your expectations (Maven 2.1, Windows, Java > 1.5): > > [ERROR] The following builds failed: > [ERROR] * it-display-dependency-updates-report-001\pom.xml known issue with new goal > [ERROR] * it-display-plugin-updates-004\pom.xml known issue, i suspect this is a bad test > [ERROR] * it-update-properties-004\pom.xml bad test > [ERROR] * it-update-properties-005\pom.xml bad test > > Ping me if you need more debug info on those ITs. > > > Benjamin > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
