It's an acceptible workaround, though you should be aware that repository grouping that you are looking for is already implemented on trunk and will be shortly released in Archiva 1.1.
- Brett 2008/6/26 Danilo Tuler <[EMAIL PROTECTED]>: > > Hi, > > How bad it is to proxy a managed repository to another managed repository? > > We set up archiva in our company, and created a "thirdparty" managed > repository to deploy third party non-public artifacts. > > 1) Should I force all our projects to include the > http://intranet/archiva/repository/thirdparty repository to each project > pom? > > 2) Or should I create a proxy from thirdparty to internal? > > My users will use mirrorOf * to internal in settings.xml. And they would > need to add an additional mirror for the thirdparty repository in case of > (1). > > Thanks, > Danilo > > -- > View this message in context: > http://www.nabble.com/Proxying-a-managed-repository-tp18133371p18133371.html > Sent from the archiva-users mailing list archive at Nabble.com. > > -- Brett Porter Blog: http://blogs.exist.com/bporter/
