You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Paul Benedict <pb...@apache.org> on 2008/11/29 20:23:46 UTC
M3: Restrict artifact groupId to TLD only?
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 like to recommend this default behavior, and allow a setting flag
to undo it. This will help organize the future, I think, a little
better.
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: M3: Restrict artifact groupId to TLD only?
Posted by Stephen Connolly <st...@gmail.com>.
of course since the tld naming rules have been relaxed so that
anything goes, is this really an issue (other than nobody, yet,
registering as the registrar for the log4j tld)
;-)
Sent from my iPod
On 30 Nov 2008, at 02:24, "Paul Benedict" <pb...@apache.org> wrote:
> 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
> <jv...@sonatype.com> wrote:
>> 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,
>>>
>>> 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 like to recommend this default behavior, and allow a setting
>>> flag
>>> to undo it. This will help organize the future, I think, a little
>>> better.
>>>
>>> Paul
>>>
>>> ---
>>> ------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> jason at sonatype dot com
>> ----------------------------------------------------------
>>
>> the course of true love never did run smooth ...
>>
>> -- Shakespeare
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: M3: Restrict artifact groupId to TLD only?
Posted by Paul Benedict <pb...@apache.org>.
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 <jv...@sonatype.com> wrote:
> 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,
>>
>> 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 like to recommend this default behavior, and allow a setting flag
>> to undo it. This will help organize the future, I think, a little
>> better.
>>
>> Paul
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
> the course of true love never did run smooth ...
>
> -- Shakespeare
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: M3: Restrict artifact groupId to TLD only?
Posted by Jason van Zyl <jv...@sonatype.com>.
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,
>
> 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 like to recommend this default behavior, and allow a setting flag
> to undo it. This will help organize the future, I think, a little
> better.
>
> Paul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
the course of true love never did run smooth ...
-- Shakespeare
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org