Re: Maven Eclipse Plugin Final Release ?
> On Apr 30, 2015, at 4:25 PM, Karl Heinz Marbaise wrote: > > Hi, > > i would like to know if there are any objections to make a final release of > the maven-eclipse-plugin ? > No objections to doing the release. Objection to calling it a final release. :-) Dan > The reason is simply because it is the last plugin on the list which misses > the Maven 2.2.1 minimum > > This could make our release map complete here... > > as you can see here: > > https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisites.html > > > If there will be no objections until 8. May 2015 i will start a release on > weekend afterwards... > > Kind regards > Karl Heinz Marbaise > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Migrating to maven 3 deps
Not that I'm aware of, but I can think of several steps: - compile/runtime should not depend on maven-compat (the plugin-testing-harness still requires it, so test-scope is still required, though) - consider testing with a Maven distribution without maven-compat - use the major release to do housekeeping: remove deprecated parameters, use direct M3 method calls instead of by reflection. I'm working on artifact/dependency related issues for the install, invoker and deploy plugins. I've created branches for these to give me enough time to fix this correctly. thanks, Robert Op Thu, 30 Apr 2015 22:29:18 +0200 schreef Kristian Rosenvold : Do we have any wiki page describing the migration steps that would be recommended to move a plugin from 2.2.1 deps to 3.x deps ? I'm thinking *both* in terms of avoiding deprecations and "other" troubles that may arise ? Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Migrating to maven 3 deps
Do we have any wiki page describing the migration steps that would be recommended to move a plugin from 2.2.1 deps to 3.x deps ? I'm thinking *both* in terms of avoiding deprecations and "other" troubles that may arise ? Kristian
Maven Eclipse Plugin Final Release ?
Hi, i would like to know if there are any objections to make a final release of the maven-eclipse-plugin ? The reason is simply because it is the last plugin on the list which misses the Maven 2.2.1 minimum This could make our release map complete here... as you can see here: https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisites.html If there will be no objections until 8. May 2015 i will start a release on weekend afterwards... Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Do we want to go for gitpubsub?
My read is this work much like Github pages works. You have a repository with your source and the rendered pages go into a branch. But nothing stops you from having the source in one repo and just pushing the generated content to another repo. This is currently how we do the M2Eclipse site. We have a Jekyll site in one repository, and we have a process that runs Jekyll and produces the website which gets pushed. I think if we did the same it would be cool because we could have the site on Github where we can use Jekyll, let people make pull requests and push it back here for official publishing. On Apr 30, 2015, at 2:55 PM, Michael Osipov wrote: > Am 2015-04-30 um 00:31 schrieb Stephen Connolly: >> http://bit.ly/1QLwWGS >> >> (Source: https://twitter.com/planetapache/status/593535338074611712) > > Wouldn't that imply always to clone a private copy of the entire repo with > autogerated stuff just to push changes back to the canonical repo? > > Sounds like an absolute waste of time and resources to me. > > Michael > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > Thanks, Jason -- Jason van Zyl Founder, Takari and Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - A language that doesn’t affect the way you think about programming is not worth knowing. -- Alan Perlis - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Do we want to go for gitpubsub?
Am 2015-04-30 um 00:31 schrieb Stephen Connolly: http://bit.ly/1QLwWGS (Source: https://twitter.com/planetapache/status/593535338074611712) Wouldn't that imply always to clone a private copy of the entire repo with autogerated stuff just to push changes back to the canonical repo? Sounds like an absolute waste of time and resources to me. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
