This has been done from the very beginning. Actually, I created an archiva user and assigned that user the role of "repository manager" and set up the settings.xml like you have described. This has not worked.
Do I need to make the user a "repository observer" also? Are there logging options that might help me determine if archiva is even getting the request to proxy a request? Maria Odea Ching-5 wrote: > > Sorry, I forgot to include that you need to do either of these two: > 1. Grant the repository observer role for your repo to user 'guest', OR > 2. Create a user in Archiva and assign it with the repository observer > role > for your repo, then set this in your settings.xml as well: > <server> > <id>[REPO_ID]</id> > <username>[USERNAME]</username> > <password>[PASSWORD]</password> > </server> > > -Deng > > On Feb 5, 2008 11:56 PM, Doug Knesek <[EMAIL PROTECTED]> wrote: > >> >> I've essentially done all of the steps you listed. But my builds fail >> immediately with: >> >> [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for >> updates from central >> [WARNING] repository metadata for: 'artifact >> org.apache.plugins:maven-clean-plugin' could not be retrieved from >> repository: central due to an error: Error transferring file >> [INFO] Repository 'central' will be blacklisted >> [INFO] ---------------------------------------- >> [ERROR] BUILD ERROR >> >> I am using Maven 2.0.8. I there something special I have to do for >> plugins? >> >> >> Maria Odea Ching-5 wrote: >> > >> > Hi Doug, >> > >> > To force Maven to use only your Archiva managed repository (if you >> don't >> > want to use the pre-configured 'internal' repository), you need to do >> the >> > ff: >> > 1. Create a managed repository in Archiva >> > 2. By default, the central and java.net repos are already >> pre-configured. >> > You can add another remote repository you want to proxy though. >> > 3. In the Proxy Connectors page, create a new proxy connector. Set the >> > managed repo you've added to proxy a remote repository from the list. >> > 4. Set the following in your settings.xml file: >> > >> > <mirrors> >> > <mirror> >> > <id>[REPO_ID]</id> >> > <url>[REPO_WEBDAV_URL]</url> >> > <mirrorOf>*</mirrorOf> >> > </mirror> >> > </mirrors> >> > >> > >> > Now, to set-up a deployment repository managed by Archiva.. >> > 1. Create a new managed repo in Archiva >> > 2. Then set the webdav url of this managed repo in the >> > <distributionManagement> section of your project's pom >> > >> > HTH, >> > Deng >> > >> > On Feb 5, 2008 3:17 AM, Doug Knesek <[EMAIL PROTECTED]> wrote: >> > >> >> >> >> I find the settings in the documentation about repository proxying to >> be >> >> unclear. Here is what I'm trying to do: >> >> >> >> I want to force all my maven repository lookups to go through archiva >> - >> >> but >> >> I want it to behave just like a default maven installation except that >> I >> >> want my own deployments to be reside on my own repository managed by >> >> archiva. >> >> >> >> What maven/archiva settings would be required to make this happen? >> >> >> >> Thank you, >> >> - Doug >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Basic-Repository-Proxying-settings-tp15275126p15275126.html >> >> Sent from the archiva-users mailing list archive at Nabble.com. >> >> >> >> >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Basic-Repository-Proxying-settings-tp15275126p15291547.html >> Sent from the archiva-users mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/Basic-Repository-Proxying-settings-tp15275126p15312074.html Sent from the archiva-users mailing list archive at Nabble.com.
