. Fox [mailto:[EMAIL PROTECTED]
Sent: Thu 4/10/2008 01:52
To: Maven Users List
Subject: RE: Deploying a modified plugin to an in-house repository
The url was an artifactory one...
-Original Message-
From: Nick Stolwijk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 09, 2008 6:05 PM
to an in-house repository
The url was an artifactory one...
-Original Message-
From: Nick Stolwijk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 09, 2008 6:05 PM
To: Maven Users List
Subject: Re: Deploying a modified plugin to an in-house repository
Doesn't deploying to archiva require the webdav
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 \
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 \
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
The url was an artifactory one...
-Original Message-
From: Nick Stolwijk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 09, 2008 6:05 PM
To: Maven Users List
Subject: Re: Deploying a modified plugin to an in-house repository
Doesn't deploying to archiva require the webdav wagon
