Hi, generally it is, what I'm looking for and I'm doing that already. I'm using Apache Archiva as my repository manager and i defined several repositories in several profiles in my one central settings.xml. The problem is, they are NOT independent, because localRepository connects them and their content in one single repository. Every artifact built with maven and deployed in any of these repositories is also in localRepository and will be found there, if it is allowed or not. Stephen is right, we have a different use of versions and repositories, which is not the same, maven expects. So my solution now was to eliminate our company-internal artifacts from localRepository, before every build. (We might test release-plugin in future. But at the moment there are deadlines for a functional system ...)
Well it works :-) Thanks for your help. mkr wrote: > > Not sure I understood this correctly. It appears that you want to have a > 1..n RELEASE > repositories, that are access controlled. There are couple of ways you can > go about > it (I think): > - if you use a Repository Manager like Nexus, you can get what you want, > maintaining > the same "settings.xml" > - Or you can always have a settings.xml with various mirror settings. Or > there are also > options available in the Maven Client command to *override* the > default > settings.xml > locations. > Don't know if that is what you are looking for. > > Thanks, > mohan kr > -- View this message in context: http://www.nabble.com/Can-I-prevent-maven-from-searching-dependencies-in-localRepository--tp24054742p24086827.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]
