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, Robert Scholte <codeh...@sourcegrounds.com> wrote: > 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 the community. > However, the plugin only works if: > - it is in Maven central > - the user can or is allowed to connect to Maven Central (users with a > Repository Manager are kind of doomed) > Otherwise the user still has to define its own settings.xml. > So here we have our chicken-egg problem, though I still think that the > base is good. > > So the "mojo" part of the name of your plugin means actually Mojo as in > Maven-Plugin instead of the Codehaus Mojo team. > I still think that "prepare-environment" is correct, but you should be > able to add an argument for which certificates should be installed. So " > codehaus.org" should map to the already specified URL's. > The prepare-eclipse is actually also Codehaus Mojo specific. > The only general thing is prepare-project, which could be enriched with > other scm types. > > IMHO we should make a decision: either make it for the mojo-team only and > don't push it to Maven Central or make it for maven-plugin development in > general and make it more configurable, e.g. by URL. > > Robert > > [1] http://mojo.codehaus.org/setup/setup-maven-plugin/index.html > > Op Sun, 29 Jun 2014 01:20:57 +0200 schreef Dan Tran <dant...@gmail.com>: > > > Hi Robert, >> >> I think this plugin is helpful for those using Maven code style. Apache >> Maven and MOJO dev team can use it.. >> >> I also has the another Maven SCM Provider for Perforce using P4Java hosted >> at workshop.perforce.com >> >> That is why it is needed at Maven Central. >> >> The only unrelated goal is prepare-environment, perhaps I should change it >> back to 'import-codehaus-certificates. >> >> Thoughts? >> >> Thanks >> >> -Dan >> >> >> >> On Sat, Jun 28, 2014 at 3:08 AM, Robert Scholte < >> codeh...@sourcegrounds.com> >> wrote: >> >> I agree with Baptiste here. >>> >>> I'm also wondering if this project should be pushed to Maven central, >>> since it's first of all a codehaus mojo specific plugin. >>> >>> so -1 >>> >>> Robert >>> >>> >>> Op Sat, 28 Jun 2014 00:19:47 +0200 schreef Baptiste Mathus < >>> bapti...@codehaus.org>: >>> >>> I'm not personally worried, actually. I didn't make the rules BTW, I'm >>> >>>> still a newcomer here. I don't know the discussions that came to define >>>> that process neither, but let's just say that would be simpler next time >>>> to >>>> just stick to it I suppose. It's not that he heavyweight IMO. >>>> >>>> So I won't vote -1 just for that, sure. Just carry on if nobody else >>>> complains. >>>> >>>> Thanks for the work. >>>> >>>> Cheers >>>> Le 28 juin 2014 00:13, "Dan Tran" <dant...@gmail.com> a écrit : >>>> >>>> I would like do it in one shot for this small mojo. Unless you'd like >>>> >>>>> me >>>>> to rephase vote, or create 2 votes >>>>> >>>>> -D >>>>> >>>>> >>>>> On Fri, Jun 27, 2014 at 3:06 PM, Baptiste Mathus <bmat...@batmat.net> >>>>> wrote: >>>>> >>>>> I hate doing that, and hope I just missed it: didn't you forget to >>>>> first >>>>> >>>>>> call a vote to just go out of sandbox? >>>>>> >>>>>> >>>>>> http://mojo.codehaus.org/development/performing-a- >>>>>> release.html#Graduating_from_the_Sandbox >>>>>> >>>>>> Cheers >>>>>> >>>>>> >>>>>> 2014-06-26 22:51 GMT+02:00 Garvin LeClaire <garvin.lecla...@gmail.com >>>>>> >: >>>>>> >>>>>> +1 >>>>>> >>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> >>>>>>> Garvin LeClaire >>>>>>> garvin.lecla...@gmail.com >>>>>>> >>>>>>> >>>>>>> On Thu, Jun 26, 2014 at 1:30 AM, Dan Tran <dant...@gmail.com> wrote: >>>>>>> >>>>>>> >>>>>>> Hi >>>>>>>> >>>>>>>> I would like cut the first beta release of this mojodev-maven-plugin >>>>>>>> which has a number of productivity goals used by >>>>>>>> Codehaus'MOJO/Apache >>>>>>>> Maven teams. >>>>>>>> >>>>>>>> >>>>>>>> Staging Repositories: >>>>>>>> General: https://nexus.codehaus.org/content/groups/staging/ >>>>>>>> Exclusive: *https://nexus.codehaus.org/content/repositories/ >>>>>>>> orgcodehausmojo-1101 >>>>>>>> <https://nexus.codehaus.org/content/repositories/ >>>>>>>> orgcodehausmojo-1101 >>>>>>>> >* >>>>>>>> >>>>>>>> >>>>>>>> (Staging) Site: >>>>>>>> http://mojo.codehaus.org/mojodev-maven-plugin/ >>>>>>>> >>>>>>>> SCM Tag: >>>>>>>> http://svn.codehaus.org/mojo/tags/mojodev-maven-plugin-1. >>>>>>>> <http://svn.codehaus.org/mojo/tags/mojodev-maven-plugin-1.0-beta-1> >>>>>>>> >>>>>>>> 0-beta-1 >>>>>>>> >>>>>>>> [ ] +1 >>>>>>>> [ ] +0 >>>>>>>> [ ] -1 >>>>>>>> >>>>>>>> The vote is open for 72 hours and will succeed by lazy consensus. >>>>>>>> >>>>>>>> Kind regards >>>>>>>> >>>>>>>> -Dan >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> -- >>>>>> Baptiste <Batmat> MATHUS - http://batmat.net >>>>>> Sauvez un arbre, >>>>>> Mangez un castor ! >>>>>> >>>>>> >>>>>> >>>>> --------------------------------------------------------------------- >>> 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 > > >
