There are no plans to remove it. Only the to try and make it more convenient if possible and make the error messages little more clear.
jvz On 2011-10-23, at 5:37 PM, Stefan <[email protected]> wrote: > Hi guys, > > Currently, we're migrating our Archiva to Nexus and I happened to observe the > builds used by different teams lately. >> I fear there is no perfect solution. If e.g. 2 projects use the same repo-id >> and point to different URLs, then this would also cause inconsistency. But I >> think this problem is more theoretic than practically relevant. > Turns out, that there are projects where people have declared our snapshots > repository with id "internal" which is naturally assigned to the internal > repo - maybe because the credentials for both are the same. So here's an > example from practice. > > And if I can advocate for keeping this feature - I like it a lot, because we > have certain devs, who sometimes build projects locally and forget to deploy > them, which results in broken builds. Also, this feature helped me convince > the management, why to upgrade to maven 3. > > Cheers, > Stefan > > > > > --------------------------------------------------------------------- > 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]
