Re: [M2- MVN Deploy Problem Error Code 201]
To be honest, I'm not sure how to proceed either.
HTTP 201 is a success code meaning created. Perhaps the
DeployMojo.java code is only written to handle HTTP 200 ok? Might
want to check the code yourself just to see what's going on there...
Check JIRA for this bug and if its not there, I'd file it. Include
this stacktrace below.
Wayne
On 10/16/06, Sebastian Krebs [EMAIL PROTECTED] wrote:
Hi,
now I get this, but I can make nothing of it :-)
Here is my stacktrace:
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from QIR
[DEBUG] repository metadata for: 'snapshot xx.yy:zz:1.0.0-SNAPSHOT' could not
be found on repository: QIR
[DEBUG] not adding permissions to wagon connection
Uploading:
http://{myHost}/xx/yy/zz/1.0.0-SNAPSHOT/zz-1.0.0-20061016.051508-1.jar
25K uploaded
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error deploying artifact: Unable to transfer file. HttpURLConnection
returned the response code: 201
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
artifact: Unable to transfer file. HttpURLConnection retur
ned the response code: 201
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error deploying
artifact: Unable to transfer file. HttpURLConnection re
turned the response code: 201
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:145)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
... 16 more
Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException:
Error deploying artifact: Unable to transfer file. Http
URLConnection returned the response code: 201
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:91)
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:133)
... 18 more
Caused by: org.apache.maven.wagon.TransferFailedException: Unable to transfer
file. HttpURLConnection returned the response code:
201
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.put(LightweightHttpWagon.java:143)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:180)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77)
... 19 more
[INFO]
[INFO] Total time: 14 seconds
[INFO] Finished at: Mon Oct 16 07:15:19 CEST 2006
[INFO] Final Memory: 5M/9M
[INFO]
Sebastian
-Ursprüngliche Nachricht-
Von: Wayne Fay [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 13. Oktober 2006 16:45
An: Maven Users List
Betreff: Re: [M2- MVN Deploy Problem Error Code 201]
Try it again using mvn -X for additional debugging information that
might be useful.
Wayne
On 10/13/06, Sebastian Krebs [EMAIL PROTECTED] wrote:
Hi together,
I've got the following problem using M2.0.4
I want
Re: [M2- MVN Deploy Problem Error Code 201]
PROTECTED] Gesendet: Freitag, 13. Oktober 2006 16:45 An: Maven Users List Betreff: Re: [M2- MVN Deploy Problem Error Code 201] Try it again using mvn -X for additional debugging information that might be useful. Wayne On 10/13/06, Sebastian Krebs [EMAIL PROTECTED] wrote: Hi together, I've got the following problem using M2.0.4 I want to deploy an artefact into my remote repository using mvn deploy. Normally, or as I had understood, M2 will deploy the resulting jar and the needed *.pom files. When I'm calling mvn deploy, M2 only copies the resulting jar into my repo. After copying, M2 results in an error code of 201. So M2 don't copy the other needed files, so further projects will not find the artefact in my remote repo. Maybe Maven stops to copy the other files, because of getting an error while sending the first file ??? Did anyone know this problem ? Regards Sebastian Krebs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: [M2- MVN Deploy Problem Error Code 201]
Hi,
now I get this, but I can make nothing of it :-)
Here is my stacktrace:
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from QIR
[DEBUG] repository metadata for: 'snapshot xx.yy:zz:1.0.0-SNAPSHOT' could not
be found on repository: QIR
[DEBUG] not adding permissions to wagon connection
Uploading:
http://{myHost}/xx/yy/zz/1.0.0-SNAPSHOT/zz-1.0.0-20061016.051508-1.jar
25K uploaded
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error deploying artifact: Unable to transfer file. HttpURLConnection
returned the response code: 201
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
artifact: Unable to transfer file. HttpURLConnection retur
ned the response code: 201
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error deploying
artifact: Unable to transfer file. HttpURLConnection re
turned the response code: 201
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:145)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
... 16 more
Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException:
Error deploying artifact: Unable to transfer file. Http
URLConnection returned the response code: 201
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:91)
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:133)
... 18 more
Caused by: org.apache.maven.wagon.TransferFailedException: Unable to transfer
file. HttpURLConnection returned the response code:
201
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.put(LightweightHttpWagon.java:143)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:180)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77)
... 19 more
[INFO]
[INFO] Total time: 14 seconds
[INFO] Finished at: Mon Oct 16 07:15:19 CEST 2006
[INFO] Final Memory: 5M/9M
[INFO]
Sebastian
-Ursprüngliche Nachricht-
Von: Wayne Fay [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 13. Oktober 2006 16:45
An: Maven Users List
Betreff: Re: [M2- MVN Deploy Problem Error Code 201]
Try it again using mvn -X for additional debugging information that
might be useful.
Wayne
On 10/13/06, Sebastian Krebs [EMAIL PROTECTED] wrote:
Hi together,
I've got the following problem using M2.0.4
I want to deploy an artefact into my remote repository using mvn deploy.
Normally, or as I had understood, M2 will deploy the resulting jar and
the needed *.pom files.
When I'm calling mvn deploy, M2 only copies the resulting jar into my
repo.
After copying, M2 results in an error code of 201.
So M2 don't copy the other needed files, so further projects
[M2- MVN Deploy Problem Error Code 201]
Hi together, I've got the following problem using M2.0.4 I want to deploy an artefact into my remote repository using mvn deploy. Normally, or as I had understood, M2 will deploy the resulting jar and the needed *.pom files. When I'm calling mvn deploy, M2 only copies the resulting jar into my repo. After copying, M2 results in an error code of 201. So M2 don't copy the other needed files, so further projects will not find the artefact in my remote repo. Maybe Maven stops to copy the other files, because of getting an error while sending the first file ??? Did anyone know this problem ? Regards Sebastian Krebs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2- MVN Deploy Problem Error Code 201]
Try it again using mvn -X for additional debugging information that might be useful. Wayne On 10/13/06, Sebastian Krebs [EMAIL PROTECTED] wrote: Hi together, I've got the following problem using M2.0.4 I want to deploy an artefact into my remote repository using mvn deploy. Normally, or as I had understood, M2 will deploy the resulting jar and the needed *.pom files. When I'm calling mvn deploy, M2 only copies the resulting jar into my repo. After copying, M2 results in an error code of 201. So M2 don't copy the other needed files, so further projects will not find the artefact in my remote repo. Maybe Maven stops to copy the other files, because of getting an error while sending the first file ??? Did anyone know this problem ? Regards Sebastian Krebs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
