Re: [mojo-dev] [VOTE] Release MOJODEV Maven Plugin - Release 1.0-beta-1 (take 2)

2014-06-29 Thread Robert Scholte
Hi Dan, I see some comparison with one of my old plugins. About 2,5 years ago I started the setup-maven-plugin[1] Main reasons were: - the maven-install-plugin doesn't install Maven. - there are a lot of unknown configuration files for Maven. By bundling these into 1 plugin I hoped it could help

Re: [mojo-dev] [VOTE] Release MOJODEV Maven Plugin - Release 1.0-beta-1 (take 2)

2014-06-29 Thread Dan Tran
I advocate to push it to maven central since other project can use it as well including my internal plugin development. BTW, I have a really need for this. What would it take todo so? should we push it as alpha while waiting for more concrete decision? -D On Sun, Jun 29, 2014 at 2:33 AM, Ro

Re: [mojo-dev] [VOTE] Release MOJODEV Maven Plugin - Release 1.0-beta-1 (take 2)

2014-06-29 Thread Robert Scholte
This is exactly the reason why there is a separate phase for getting plugins out of the sandbox. I often hear people complaining about backwards compatibility, so we should at least try to have a clear vision on this plugin. For now I'd say: - remove the prepare-environment goal, since environ

[mojo-dev] [jira] (MAPPASM-231) Use manifest-only jars for classpath

2014-06-29 Thread Benson Margulies (JIRA)
Title: Message Title Benson Margulies commented on an issue

[mojo-dev] [jira] (MLICENSE-108) copyright owner is not working properly

2014-06-29 Thread JIRA
Title: Message Title Cristiano Gavião created an issue

Re: [mojo-dev] [VOTE] Release MOJODEV Maven Plugin - Release 1.0-beta-1 (take 2)

2014-06-29 Thread Dan Tran
I must admin i am rushing to push it to Central since there is another project at workshop.perforce.com that I like to use prepare-eclipse officially ( available at central). But that can be delay to get a conscientious agreement at MOJO. Historically, I started out with this plugin due to the ne