Re: AW: [DISCUSS] MNG-3226 - Developers and Contributors information is not being inherited

I would go with the current behaviour as well. Milos On Thu, Apr 1, 2010 at 11:33 PM, Justin Edelson wrote: > +1 > > On Apr 1, 2010, at 4:21 PM, Mark Struberg wrote: > > > I think the current behaviour is the most flexible and also very > > intuitive. So I'd let it as is. > > > > LieGrue, > > s

[jira] Subscription: Design & Best Practices

Issue Subscription Filter: Design & Best Practices (22 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles http://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

Re: [DISCUSS] MNG-2103 Inheritance of overrides that of

I've often desired some additional logic here that is related and may side-step this: Think about how pluginManagement allows you to define something that only applies once a child pom "mentions" the plugin. Apply the same logic to an execution, where you could define one ore more default executio

Re: AW: [DISCUSS] MNG-3226 - Developers and Contributors information is not being inherited

+1 On Apr 1, 2010, at 4:21 PM, Mark Struberg wrote: > I think the current behaviour is the most flexible and also very > intuitive. So I'd let it as is. > > LieGrue, > strub > > --- Benjamin Bentmann schrieb am Do, > 1.4.2010: > >> Von: Benjamin Bentmann >> Betreff: [DISCUSS] MNG-3226 - Develo

AW: [DISCUSS] MNG-3226 - Developers and Contributors information is not being inherited

I think the current behaviour is the most flexible and also very intuitive. So I'd let it as is. LieGrue, strub --- Benjamin Bentmann schrieb am Do, 1.4.2010: > Von: Benjamin Bentmann > Betreff: [DISCUSS] MNG-3226 - Developers and Contributors information is not > being inherited > An: "Mave

[DISCUSS] MNG-3226 - Developers and Contributors information is not being inherited

Hi, another model building issue I would appreciate comments on. Right now, developers and contributors are only inherited if the child doesn't specify those at all. By specifying developers/contributors, a child POM has complete control of the list. If we change the behavior to merge with th

[DISCUSS] MNG-2103 Inheritance of overrides that of

Hi, I would appreciate some comments on the above issue MNG-2103 where users requested that plugin.execution.inherited generally overrides plugin.inherited. Considering the three possible values for the inherited field (true != false != null), we currently determine the inheritance of an exe

Re: Creating a pseudon-mixins plug-in problem (or how to alter the project set-up in memory)

Well, that sounds promising! I'll give that a try and see how that can help us managing our dependencies. Thanks a lot for the valuable feedback! Cheers, Mirko On Thu, Apr 1, 2010 at 3:55 PM, Ralph Goers wrote: > Yes, import scope can help with this. > > We have a pom that declares the version o

Re: Creating a pseudon-mixins plug-in problem (or how to alter the project set-up in memory)

Yes, import scope can help with this. We have a pom that declares the version of any dependency we MIGHT need. That pom gets imported to control the versions. The actual project poms then reference the dependencies they need to compile and run. When maven is building the artifact that is deplo

Re: Creating a pseudon-mixins plug-in problem (or how to alter the project set-up in memory)

It's not a perfect solution but look at placing dependencies in a separated POM and pulling that POM in as a dependency using scope = import. This mode is more compositional and mixin-like. On Apr 1, 2010, at 8:56 AM, Mirko Jahn wrote: > Hi together, > > I looked into the problem again and if

Re: Creating a pseudon-mixins plug-in problem (or how to alter the project set-up in memory)

Hi together, I looked into the problem again and if there is no way of limiting the dependencies on a more aggregated level, I believe mixins are a really important feature to look at. In my case, the parent pom with the dependency management section and configuration already has about 2.5k lines

Re: [VOTE] Release Maven Compiler Plugin 2.2

Le Tue, 30 Mar 2010 11:54:36 +0200, Milos Kleint a écrit : +1 > Hi, > > We solved 6 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11130&version=16097 > > Staging repo: > https://repository.apache.org/content/repositories/maven-00