Matt Brown-20 wrote:
>
> Why would you want Maven to NOT use the local repository? I believe it
> does this so that every single goal/phase (compile, test, etc) does not
> need to re-fetch artifacts it has already seen from the network.
>
As mentioned in my question, there are several repositories, which provide
all the artifacts a special group of developers is allowed to use. They can
use their own artifacts, stored in there own repository, external artifacts,
provided by a repository for external jars, and other (company-) internal
artifacts, created by other developer groups, but ONLY in case they think
the artifacts are reusable. So they (as the creators of a specific artifact)
have to decide which artifact in which version is usable by other groups,
and so they deploy this version of a artifact into the "share"-repository S.
Thats the scenario software-development is organized in my company.
So just for explanation: If artifact A is just built and NOT deployed into
S, it's nevertheless usable, because maven looks into localRepository. But A
IS NOT tested and NOT thought for use in other project-contexts. Thats why
I'd like to prevent maven from fetching artifacts from localRepository. It
should just use all the repository I tell maven a specific user/group IS
ALLOWED to use. If there is no possibility, I'd have to set up a
maven-instance for every group of developers, instead of using one central
installation for all groups and seperate them with different repositories
and profiles.
--
View this message in context:
http://www.nabble.com/Can-I-prevent-maven-from-searching-dependencies-in-localRepository--tp24054742p24067791.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
