| Re: [aether-users] maven aether provider deploy failed with Apache Archiva 2.0.0 |
Bk Lau wrote:
Turn out that Apache Archiva 2.0.0 changed the web context for standalone for from "/archiva" to "/" instead.
Ah, good to know.
However, this time the error message changes to: 03/05/14 21:38:41.197 SEVERE: [DefaultTransferListener] Artifact transfer failed org.eclipse.aether.transfer. ArtifactTransferException: Could not transfer artifact org.something rom/to External-Repo (http://localhost:9080/repository/internal): Bad Request (400)
Did you check whether there are any more error details in the Archiva logs that would indicate why the request is deemed bad?
Random ideas: How big is your WAR, is this by chance exceeding some default upload limit in Archiva? What version does the WAR have, SNAPSHOT vs non-SNAPSHOT, and does the destination repository accept those versions? Did you verify no files related to your deployment already exist in Archiva from prior attempts in which case Archiva might simply block re-deployment?
Frankly, I know close to nothing about Archiva and so can't help much with troubleshooting, i.e. you might also want to ping the Archiva user list about this.
Benjamin