You're right about having to put your internal repositories in
settings.xml for deploy.
maven-proxy and proximity are meant to proxy artifact/file downloads
from its proxied repositories. To deploy your artifacts, you will need
direct access to the repository ( not necessarily internal ), and after
that, the proxy cache need to be refreshed.
About your inquiry, I guess proxying internal repositories is still
helpful because you need not put your internal repositories in your
project's pom.xml.
So if you have 5 teams with their own repositories each, they need only
define one internal repository in their settings.xml each and of course
the mirror. When you don't proxy them, then each team will have one
internal repository in their settings.xml and all the five internal
repositories in their pom.xml.
^_^
Treloar, Barrie (SAPOL) wrote:
Having documentied the process I went through in creating internal
repositories and setting up maven-proxy, I wondered why you would proxy
internal repositories.
The property files available for maven-proxy include internal repositories
as part of their configuration. See
http://cvs.maven-proxy.codehaus.org/*checkout*/maven-proxy/core/src/test/res
ources/org/apache/maven/proxy/config/PropertyLoaderTest1.properties?rev=HEAD
However, to be able to deploy to the internal repositories they need to be
defined in settings.xml.
Once in settings.xml they are contacted direct instead of using maven-proxy.
So I am struggling to see any benefit in proxying internal repositories.
If someone with more maven experience and decent understanding of maven
proxy would be kind enough to read
http://docs.codehaus.org/display/MAVENUSER/Using+Maven+in+a+corporate+enviro
nment and see if what I did was sane and/or offer comments, that would be
appreciated.
Cheers
Barrie
---------------------------------------------------------------------
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]
