Stephen Nesbitt wrote:
should be visited.
I am not sure that this is fine grained enough. I can imagine a use case in which a developer has dependecies on jar A & jar B both having the same groupId with a repository tied to say QA snapshots. For whatever reason the developer decides that he wants Jar A from the bleeding edge repository while leaving Jar B from the QA repository (maybe confirming a fix to a QA issue?) In any case having the repository assigned to the groupID won't meet this case.
I'm not sure just how much of an edge case this is, but I do think it is important to have some sort of answer (even if it is a manual process of updating your local repo directly)
I am sure that it can be addressed in some way.
For example you can write your own plugin which will deploy some artifacts to QA repository
or do somthing which is needed to match coorporate standards.
I would't be expecting that maven will be out of the box supporting all possible artifact flows
in every company.
One thing which will be particulary good in m2 is that it is componetizied.
We are not sure what we will be willing to expose to end users but there are componets like
ArtifactDeployer, ArtifactInstaller, ArtifactDowloader etc and m2 will come with "default" implementation.
of that componets which define our strategy for communicating with repositories.
In case of highly no standart needs I imagine that implementation of that components can be extended or replaced
to match those unusal needs. It will be probably very, very rare case - but still it will be possible to do so.
Michal
---------------------------------------------------------------------- Startuj z INTERIA.PL!!! >>> http://link.interia.pl/f1837
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
