archiva

We are trying to use Archiva as a Maven proxy for central and other external repositories and also as a snapshot storage for our artifacts which are automatically built by Hudson from SVN and installed to the snapshot repository. I can't setup my Maven client to use the internal and snapshots repositories together. My project has some external dependencies (like log4j ) which are downloaded from the Archiva internal repository correctly. Also my project has a dependency to an own project which's artifact is already built and installed to the snapshot repository. However if i try to build the

I´m trying to publish the generated aar file of my android library to my Apache Archiva Maven server, but I haven´t manage to get it working yet because either the examples are outdated or they are for java and not for android After noticing that most methods of the gradle examples are deprecated, I found this new documentation: Gradle Documentation Which describes how to use the new API which seems to replace uploadArchives with publishing and so on.... So this is what I´ve got so far: apply plugin: 'com.android.library' apply plugin: 'maven' apply plugin: 'maven-publish' android {

This used to work before I upgraded Jenkins to 1.494. Now I get this error in Jenkins when using the build promotion plugin to copy the war artifact to the snapshot repo: ERROR: Failed to deploy artifacts: Could not transfer artifact com.blah.data:RestWebServices:war:1.0-20121224.163825-2 from/to archiva.apache.snapshots (http://10.31.31.64:8080/archiva/repository/snapshots): Failed to transfer file: http://10.31.31.64:8080/archiva/repository/snapshots/com/blah/data/RestWebServices/1.0-SNAPSHOT/RestWebServices-1.0-20121224.163825-2.war. Return code is: 401, ReasonPhrase:Unauthorized. org

I'm trying to set up a private remote repository for our team. Now the repository serves the following with so far I have tried - When a ' mvn compile ' is issued, then it searches dependencies in "~/.m2". If it is not found there then it goes to the remote private repository and when the dependencies still absent here then it goes to the central repository. Before compilation, I have to put all dependencies in our private (and remote) repository along with checksum and metadata. When we need an artifact(eg - spring-mvc), we need to put it in the remote private repository along with all

We have an internal Apache Archiva based repository and we have configured the repositories tag in pom.xml to be as follows. Can I assume that all dependency access will get resolved by internal repository if you have access to it and will get resolved by other repositories listed below, if internal repository is down for a certain reason. <repositories> <repository> <id>internal</id> <name>Internal Repository</name> <url>http://192.168.1.2/archiva/repository/internal</url> </repository> <repository> <id>jboss</id> <url>https://repository.jboss.org/nexus/content/repositories/releases</url>