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 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: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
