You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Joshua ChaitinPollak <jp...@kivasystems.com> on 2008/04/09 08:11:20 UTC
Deploying a modified plugin to an in-house repository
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/3rdp-snapshots@repo
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
Re: Deploying a modified plugin to an in-house repository
Posted by Joshua ChaitinPollak <jp...@kivasystems.com>.
This bug went away (really, it just vanished) when I upgraded to
Artifactory 1.2.5
-Josh
On Apr 10, 2008, at 3:24 AM, <ni...@planet.nl> <ni...@planet.nl>
wrote:
> Doh... Note to self: Don't post when you're tired. ;)
>
> But I see artifactory also can work with the webdav wagon. [1] Could
> you try that?
>
> Hth,
>
> Nick S.
>
> [1] http://www.jfrog.org/confluence/display/RTF/Using+Artifactory#UsingArtifactory-CLIDeployment
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> 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:nicklist@planet.nl]
> 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 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:8
> 081/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/mo
> jo/exec-maven-plugin/1.1-beta-2-SNAPSHOT/exec-maven-plugin-1.1-
> beta-2-SN
> APSHOT.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/3rdp-snapshots@repo
>>>
>>> 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-20080
> 409.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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Joshua ChaitinPollak | Software Engineer
Kiva Systems, Inc., 225 Wildwood Ave, Woburn, MA 01970
RE: Deploying a modified plugin to an in-house repository
Posted by ni...@planet.nl.
Doh... Note to self: Don't post when you're tired. ;)
But I see artifactory also can work with the webdav wagon. [1] Could you try that?
Hth,
Nick S.
[1] http://www.jfrog.org/confluence/display/RTF/Using+Artifactory#UsingArtifactory-CLIDeployment
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
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:nicklist@planet.nl]
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 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:8
081/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/mo
jo/exec-maven-plugin/1.1-beta-2-SNAPSHOT/exec-maven-plugin-1.1-beta-2-SN
APSHOT.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/3rdp-snapshots@repo
>>
>> 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-20080
409.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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Deploying a modified plugin to an in-house repository
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
The url was an artifactory one...
-----Original Message-----
From: Nick Stolwijk [mailto:nicklist@planet.nl]
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 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:8
081/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/mo
jo/exec-maven-plugin/1.1-beta-2-SNAPSHOT/exec-maven-plugin-1.1-beta-2-SN
APSHOT.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/3rdp-snapshots@repo
>>
>> 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-20080
409.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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Deploying a modified plugin to an in-house repository
Posted by Nick Stolwijk <ni...@planet.nl>.
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/3rdp-snapshots@repo
>>
>> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Deploying a modified plugin to an in-house repository
Posted by Joshua ChaitinPollak <jp...@kivasystems.com>.
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/3rdp-snapshots@repo
>
> 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
>
>
>
>
>
>
--
Joshua ChaitinPollak | Software Engineer
Kiva Systems, Inc., 225 Wildwood Ave, Woburn, MA 01970