|
»
»
»
M3: Restrict artifact groupId to TLD only?
|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
 |
M3: Restrict artifact groupId to TLD only?
by pbenedict
::
Rate this Message:
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@... For additional commands, e-mail: dev-help@... |
|
|
Re: M3: Restrict artifact groupId to TLD only?
by Jason van Zyl-5
::
Rate this Message:
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@... > For additional commands, e-mail: dev-help@... > 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@... For additional commands, e-mail: dev-help@... |
|
|
Re: M3: Restrict artifact groupId to TLD only?
by pbenedict
::
Rate this Message:
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 <jvanzyl@...> 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@... >> For additional commands, e-mail: dev-help@... >> > > 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@... > For additional commands, e-mail: dev-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: M3: Restrict artifact groupId to TLD only?
by Stephen Connolly-2
::
Rate this Message:
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" <pbenedict@...> 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 > <jvanzyl@...> 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@... >>> For additional commands, e-mail: dev-help@... >>> >> >> 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@... >> For additional commands, e-mail: dev-help@... >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
| Free Forum Powered by Nabble | Forum Help |
