On Sun, Sep 2, 2012 at 4:22 PM, Mark Struberg <strub...@yahoo.de> wrote: > This opens up another can of worms: how to deal with plugins which cannot be > made maven2 compatible anymore but we like to implement a new feature? How > long do we like to support maven2 at all? Will we create a branch for those > plugins?
The principle has to be that we can't force volunteers to volunteer, but we can make it easier. So, while we're wandering from the [VOTE], I'd propose these policies: 1: No 'gratuitous' introduction of M3 requirements. There's been plenty of email about this. 2: Make a branch for M2 releases before making the first M3 release. If someone has the itch, they can then port fixes and make releases on it without having to go spelunking to find the right rev to branch from. > > LieGrue, > strub > > > > > ----- Original Message ----- >> From: Benson Margulies <bimargul...@gmail.com> >> To: Maven Developers List <dev@maven.apache.org> >> Cc: >> Sent: Sunday, September 2, 2012 10:17 PM >> Subject: Re: [VOTE] release maven-shade-plugin version 2.0 >> >> Now we have a different problem. >> >> According to [1], the version to require Maven 3 was supposed to be >> 3.0, leaving 2.0 for a merely incompatible release that still worked >> with Maven 2.2. >> >> Folks, what's the story? Do I need to blow this up and try again as >> 3.0? Will someone fix what Hervé points to? >> >> >> >> >> [1] >> http://jira.codehaus.org/browse/MSHADE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel >> >> On Sun, Sep 2, 2012 at 11:38 AM, Hervé BOUTEMY <herve.bout...@free.fr> >> wrote: >>> 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 >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
