Re: M3: Restrict artifact groupId to TLD only?

2008-11-29 Thread Paul Benedict
But with a configuration option, you could gently guide that path :-) I am not proposing a rigid enforcement, but perhaps an exclusive M3 repository would follow this rule, where M2 would not. On Sat, Nov 29, 2008 at 5:55 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > It's always been a guideline

Re: MNG-3866: To fix or not to fix?

2008-11-29 Thread Brett Porter
On 30/11/2008, at 11:04 AM, Benjamin Bentmann wrote: Hi, In the light of MNG-3866 [0], Shane and I had a short discussion what should be the right behavior during model inheritance for handling plugin definitions with different versions. Apparently, that is something to discuss in the con

Re: MNG-3866: To fix or not to fix?

2008-11-29 Thread Jason van Zyl
On 29-Nov-08, at 4:04 PM, Benjamin Bentmann wrote: Hi, In the light of MNG-3866 [0], Shane and I had a short discussion what should be the right behavior during model inheritance for handling plugin definitions with different versions. Apparently, that is something to discuss in the conte

Re: M3: Restrict artifact groupId to TLD only?

2008-11-29 Thread Jason van Zyl
It's always been a guideline to do that, enforcing this would break too many projects. It would mean either creating a huge discontinuity between older releases, or a lot of work to convert them all. Neither is really appealing to me. On 29-Nov-08, at 11:23 AM, Paul Benedict wrote: Team,

Re: MNG-3866: To fix or not to fix?

2008-11-29 Thread Shane Isbell
My primary concern is as follows. Say there is a version 1.1 of a plugin specified in the pluginManagement section and that was joined with a plugin of version 1.0. The plugin configuration information may be completely incompatible. Also if you do the key off of version, you can define the same pl

MNG-3866: To fix or not to fix?

2008-11-29 Thread Benjamin Bentmann
Hi, In the light of MNG-3866 [0], Shane and I had a short discussion what should be the right behavior during model inheritance for handling plugin definitions with different versions. Apparently, that is something to discuss in the context of the community ;-), so please comment. In Maven 2

M3: Restrict artifact groupId to TLD only?

2008-11-29 Thread Paul Benedict
Team, What do you think of M3 dealing, by default, only with artifacts whose groupId matches valid TLD? One problem in the current M2 repo is that unimaginable places that sometimes artifacts reside in... especially when things relocate it can become quite cumbersome to navigate manually. I'd lik