Doesn't deploying to archiva require the webdav wagon instead of http wagon?
Return code 400 means:
The request could not be understood by the server due to malformed
syntax. The client SHOULD NOT repeat the request without modifications.
Take a look at the deploy to archiva page at the archiva documentation [1]
Hth,
Nick S.
[1] http://maven.apache.org/archiva/docs/1.0.2/userguide/deploy.html
Joshua ChaitinPollak wrote:
I'm still having trouble with deploying my modified exec-maven-plugin.
If I run this slightly different command line:
mvn org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy \
-DaltDeploymentRepository=plugins-snapshots::default::http://mravinjak:8081/artifactory/repo/plugins-snapshots
I get:
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error deploying artifact: Failed to transfer file:
http://mravinjak:8081/artifactory/repo/plugins-snapshots/org/codehaus/mojo/exec-maven-plugin/1.1-beta-2-SNAPSHOT/exec-maven-plugin-1.1-beta-2-SNAPSHOT.jar.
Return code is: 400
Is there anything I can do?
-Josh
On Apr 9, 2008, at 2:11 AM, Joshua ChaitinPollak wrote:
So I just made a modification to the exec-maven-plugin and now I'm
trying to share that with the rest of my company be deploying it to
our shared repository (Artifactory) with this command:
mvn org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy-file \
-DgroupId=org.codehaus.mojo -DartifactId=exec-maven-plugin \
-Dversion=1.1-beta-2-SNAPSHOT -Dpackaging=maven-plugin \
-Dfile=/Users/pardsbane/src/exec-maven-plugin/target/exec-maven-plugin-1.1-beta-2-SNAPSHOT.jar
\
-DrepositoryId=3rdp-snapshots
-Durl=http://mravinjak:8081/artifactory/repo/[EMAIL PROTECTED]
But I'm getting this error:
[INFO] Error deploying artifact: Failed to transfer file:
http://mravinjak:8081/artifactory/repo/3rdp-snapshots/org/codehaus/mojo/exec-maven-plugin/1.1-beta-2-SNAPSHOT/exec-maven-plugin-1.1-beta-2-20080409.060704-1.jar.
Return code is: 400
Which I suspect is because of the -Dpackaging=maven-plugin, but when
I tried -Dpackaging=jar, Maven wasn't able to find this version of
the plugin.
Am I doing something wrong?
--
Joshua ChaitinPollak | Software Engineer
Kiva Systems, Inc., 225 Wildwood Ave, Woburn, MA 01970
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
