Forking the other thread.
Maven still needs to work properly without a repository manager (even
if it is a good practice to use one). In my opinion, that means:
- proper unique identifiers for repositories (my preference would
actually be to control this by group ID, but I see too many counter
examples in the Maven repositories to make this realistic - if anyone
has ideas on this front please say so).
- proper mirroring support (ie, specify which mirror you want to use
for central, etc so you can get a nearby one out of the box, like
CPAN, yum, etc type setups - I have some hand written notes from some
time back sitting on my desk I can kick into the wiki)
- full control over the repositories you use from the settings file.
When it comes to handling repositories in POMs - I think they should
still be in there, but only be a hint. ie, if the repo with that ID is
not configured, Maven can intelligently tell you how to configure it
if you want to, and the consequences of doing so. But I'm sure there
are plenty of other ways we could deal with this.
On top of this, explicit support for repository managers (that
supports all of them) as a way to replace one or all of your
repositories should be available and encouraged.
Are these all the use cases folks see?
- Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
