You’r probably right about the tool integration, but I don’t think that password resolving as mention in the issue counts as a tool integration. I strongly believe this should be configurable in the settings.xml - which does not mean it must be the only place. Domi
On 23.01.2014, at 20:09, Igor Fedorenko <i...@ifedorenko.com> wrote: > Not for tooling integration usecase. There is usually a tight coupling > between version of the tool, like m2e, and the version of extension > getting pushed into maven core. So it should be the tool, not user, who > decides what extensions should be pushed. > > There are usecases for user-configurable extensions like you suggest, > but I do not believe stuffing them in settings.xml is a good idea. I > believe separate set of config files, one per extension, is a better > idea. I actually had this implemented some time ago but never got around > to commit to public repo. It may actually happen, now that you reminded > me about this, but no promise :-) > > -- > Regards, > Igor > > On 1/23/2014, 14:03, Dominik Bartholdi wrote: >> Would it not be nice to be able to configure such stuff in the settings.xml? >> and other thing like this is described in this issue: >> https://jira.codehaus.org/browse/MNG-5356 (plus an extension is mention in >> the comments) >> Configuring this in the settings.xml would allow to have a single >> configuration for a e.g. a build slave >> Domi >> >> On 23.01.2014, at 19:50, Thiebaud, Christophe <christophe.thieb...@sap.com> >> wrote: >> >>> FYI, the use-case for EventSpies @ SAP is exactly the one described by Igor >>> : we use an event spy to instrument our Hudson/Jenkins instance to monitor >>> the builds. >>> >>> This instrumentation MUST NOT require any pom.xml modification, >>> so any maven project thrown into the Hudson/Jenkins can be monitored, >>> nor any customization of the maven distribution (other than dropping files >>> in lib/ext or setting maven.ext.class.path), >>> so that maven is easy to upgrade. >>> >>> Regards >>> Christophe >>> >>> -----Original Message----- >>> From: Igor Fedorenko [mailto:i...@ifedorenko.com] >>> Sent: Donnerstag, 23. Januar 2014 15:43 >>> To: dev@maven.apache.org >>> Subject: Re: Maven 4.0.0 >>> >>> I think there are two separate concerns/usecases here. >>> >>> Tools like m2e, netbeans or hudson need a way to push core components >>> without changing maven distribution or project pom.xml files. I think >>> system properties is the most straightforward way to do this. >>> >>> Existing event listener mechanisms are convoluted and inconsistent. I >>> have to agree with this one, but I think we can offer clean(er) event >>> listener interface(s) which will work the same way regardless how >>> clients choose to contribute them to the system, via build extension, >>> system property or custom distribution. >>> >>> -- >>> Regards, >>> Igor >>> >>> On 1/23/2014, 9:27, Jason van Zyl wrote: >>>> You either end up with a custom distribution and/or using system >>>> properties. Aside from the eventing mechanism being too convoluted, >>>> something where an extension can be specified in the POM and >>>> downloaded if required would be more consistent. The custom >>>> distribution route or having to invoke Maven using a system property >>>> IMO always ends up being more difficult than necessary. Additionally >>>> we have 4-5 different entities for eventing, I would just like one >>>> consistent one given everything we know now. > >>>> On Jan 23, 2014, at 2:18 AM, Milos Kleint <mkle...@gmail.com> wrote: >>>> >>>>> EventSpies are not useless, I use them in netbeans extensively. I >>>>> inject them using maven.ext.class.path property >>>>> >>>>> Milos >>>>> >>>>> >>>>> On Thu, Jan 23, 2014 at 3:57 AM, Jason van Zyl <ja...@takari.io> wrote: >>>>>> I know there is the roadmap page >>>>>> (https://cwiki.apache.org/confluence/display/MAVEN/Roadmap), but I >>>>>> started a Maven 4.0.0 page with some general notes and I just want to >>>>>> hook in the JIRA macro to pull in all the 4.0.0 issues at the bottom, >>>>>> but I have figured that out yet. I just want to be able to write notes >>>>>> and and see the issues, and turn them into issues when appropriate. If >>>>>> anyone knows how to embed the macro the page I'd appreciate if you can >>>>>> tweak this page: >>>>>> >>>>>> https://cwiki.apache.org/confluence/display/MAVEN/Maven+4.0.0 >>>>>> >>>>>> Back to cleaning up JIRA. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Jason >>>>>> >>>>>> ---------------------------------------------------------- >>>>>> Jason van Zyl >>>>>> Founder, Apache Maven >>>>>> http://twitter.com/jvanzyl >>>>>> http://twitter.com/takari_io >>>>>> --------------------------------------------------------- >>>>>> >>>>>> We know what we are, but know not what we may be. >>>>>> >>>>>> -- Shakespeare >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> 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, Apache Maven >>>> http://twitter.com/jvanzyl >>>> http://twitter.com/takari_io >>>> --------------------------------------------------------- >>>> >>>> The modern conservative is engaged in one of man's oldest exercises in >>>> moral philosophy; that is, >>>> the search for a superior moral justification for selfishness. >>>> >>>> -- John Kenneth Galbraith >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
