Sorry, I'm -0 about this: the plugin requires Maven 3 but uses an "old" dependency-tree which is not really Maven 3 compatible
I updated the dependency in r1379995 Notice I manually removed extra directories in staging site Regards, Hervé Le vendredi 31 août 2012 18:00:45 Benson Margulies a écrit : > We solved 4 issues: > > ** Bug > * [MSHADE-103] - maven-shade-plugin does not resolve from > user-defined repositories > * [MSHADE-124] - Need better plan for getting > dependency-reduced-pom.xml out of basedir > * [MSHADE-130] - Mark mojo as threadSafe for parallel builds > > ** New Feature > * [MSHADE-112] - New property to enable shading the java text > inside the sources artifact (not just shading the java source file > locations) > > > There are still plenty more fish in this sea. > > Stating repo: > > https://repository.apache.org/content/repositories/maven-026/ > https://repository.apache.org/content/repositories/maven-026/org/apache/mave > n/plugins/maven-shade-plugin/2.0/maven-shade-plugin-2.0-source-release.zip > > Staging site: > http://maven.apache.org/plugins/maven-shade-plugin-2.0/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org
