You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/11/25 16:31:55 UTC
[jira] Created: (MNG-4469) [regression] deploy:deploy-file fails
with secured repository
[regression] deploy:deploy-file fails with secured repository
-------------------------------------------------------------
Key: MNG-4469
URL: http://jira.codehaus.org/browse/MNG-4469
Project: Maven 2
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 3.0-alpha-5
Reporter: Benjamin Bentmann
{{deploy:deploy-file}} or any other mojo that creates artifact repositories on its own will appear to ignore mirror, proxy and authentication infos from the settings when run with Maven 3.0. This is due to the {{ArtifactRepositoryFactory}} and the {{WagonManager}} being stateless and not injecting these infos any longer automatically.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-4469) [regression]
deploy:deploy-file fails with secured repository
Posted by "Stephan Weber (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208311#action_208311 ]
Stephan Weber edited comment on MNG-4469 at 1/27/10 5:23 AM:
-------------------------------------------------------------
just tried the new version of maven 3 alpha 6
mvn eclipse:to-maven -DdeployTo=man-uploads::default::http://leanserver.wdf.sap.corp:8081/nexus/content/repositories/man-uploads -DeclipseDir="C:\eclipse350"
still does only work if nexus security is switched off
was (Author: weber):
(2010.01.27): just tried the new version of maven 3 alpha 6
mvn eclipse:to-maven -DdeployTo=man-uploads::default::http://leanserver.wdf.sap.corp:8081/nexus/content/repositories/man-uploads -DeclipseDir="C:\eclipse350"
still does only work if nexus security is switched off
> [regression] deploy:deploy-file fails with secured repository
> -------------------------------------------------------------
>
> Key: MNG-4469
> URL: http://jira.codehaus.org/browse/MNG-4469
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0-alpha-5
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-6
>
>
> {{deploy:deploy-file}} or any other mojo that creates artifact repositories on its own will appear to ignore mirror, proxy and authentication infos from the settings when run with Maven 3.0. This is due to the {{ArtifactRepositoryFactory}} and the {{WagonManager}} being stateless and not injecting these infos any longer automatically.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-4469) [regression]
deploy:deploy-file fails with secured repository
Posted by "Stephan Weber (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208311#action_208311 ]
Stephan Weber edited comment on MNG-4469 at 1/27/10 5:35 AM:
-------------------------------------------------------------
just tried the new version of maven 3 alpha 6
mvn eclipse:to-maven -DdeployTo=man-uploads::default::http://localhost:8081/nexus/content/repositories/man-uploads -DeclipseDir="C:\eclipse350"
still does only work if nexus security is switched off
was (Author: weber):
just tried the new version of maven 3 alpha 6
mvn eclipse:to-maven -DdeployTo=man-uploads::default::http://leanserver.wdf.sap.corp:8081/nexus/content/repositories/man-uploads -DeclipseDir="C:\eclipse350"
still does only work if nexus security is switched off
> [regression] deploy:deploy-file fails with secured repository
> -------------------------------------------------------------
>
> Key: MNG-4469
> URL: http://jira.codehaus.org/browse/MNG-4469
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0-alpha-5
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-6
>
>
> {{deploy:deploy-file}} or any other mojo that creates artifact repositories on its own will appear to ignore mirror, proxy and authentication infos from the settings when run with Maven 3.0. This is due to the {{ArtifactRepositoryFactory}} and the {{WagonManager}} being stateless and not injecting these infos any longer automatically.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4469) [regression] deploy:deploy-file fails
with secured repository
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213534#action_213534 ]
Benjamin Bentmann commented on MNG-4469:
----------------------------------------
Anders, would you describe is a duplicate of MNG-4571.
> [regression] deploy:deploy-file fails with secured repository
> -------------------------------------------------------------
>
> Key: MNG-4469
> URL: http://jira.codehaus.org/browse/MNG-4469
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0-alpha-5
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-6
>
>
> {{deploy:deploy-file}} or any other mojo that creates artifact repositories on its own will appear to ignore mirror, proxy and authentication infos from the settings when run with Maven 3.0. This is due to the {{ArtifactRepositoryFactory}} and the {{WagonManager}} being stateless and not injecting these infos any longer automatically.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4469) [regression] deploy:deploy-file fails
with secured repository
Posted by "Anders Hammar (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213521#action_213521 ]
Anders Hammar commented on MNG-4469:
------------------------------------
I can confirm that a deploy with altDeploymentRepository doesn't not work with auth in Maven 3.0-alpha-6. It does work with Maven 2.2.1 though.
Here my command:
mvn deploy -DaltDeploymentRepository=repo-xxx::default::http://repo-xxx/content/repositories/releases
A server with id 'repo-xxx' is defined in my settings.xml.
In Nexus I see that the access is with no auth info (Nexus says anonymous).
Should this issue be reopened or do you want me to submit a new jira?
> [regression] deploy:deploy-file fails with secured repository
> -------------------------------------------------------------
>
> Key: MNG-4469
> URL: http://jira.codehaus.org/browse/MNG-4469
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0-alpha-5
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-6
>
>
> {{deploy:deploy-file}} or any other mojo that creates artifact repositories on its own will appear to ignore mirror, proxy and authentication infos from the settings when run with Maven 3.0. This is due to the {{ArtifactRepositoryFactory}} and the {{WagonManager}} being stateless and not injecting these infos any longer automatically.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-4469) [regression] deploy:deploy-file fails
with secured repository
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4469.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0-alpha-6
Assignee: Benjamin Bentmann
Fixed in [r888488|http://svn.apache.org/viewvc?view=revision&revision=888488].
> [regression] deploy:deploy-file fails with secured repository
> -------------------------------------------------------------
>
> Key: MNG-4469
> URL: http://jira.codehaus.org/browse/MNG-4469
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0-alpha-5
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-6
>
>
> {{deploy:deploy-file}} or any other mojo that creates artifact repositories on its own will appear to ignore mirror, proxy and authentication infos from the settings when run with Maven 3.0. This is due to the {{ArtifactRepositoryFactory}} and the {{WagonManager}} being stateless and not injecting these infos any longer automatically.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4469) [regression] deploy:deploy-file fails
with secured repository
Posted by "Sarath Chandra (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237725#action_237725 ]
Sarath Chandra commented on MNG-4469:
-------------------------------------
Looks like it is still an issue. I get this when trying to upload to nexus
Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not transfer artifact serra:serra-we:jar:1.10-20101006.213417-2 from snapshots (http://serra.we/nexus/content/repositories/snapshots, releases=true, snapshots=true, managed=false): Error transferring file
at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:860)
at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:851)
at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.flush(WagonRepositoryConnector.java:775)
at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:389)
at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:223)
... 24 more
Caused by: org.apache.maven.wagon.TransferFailedException: Error transferring file
at org.apache.maven.wagon.providers.http.LightweightHttpWagon.finishPutTransfer(LightweightHttpWagon.java:213)
at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:413)
at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:392)
at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:365)
at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:163)
at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:736)
at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:388)
... 25 more
Caused by: java.io.IOException: Error writing to server
at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:468)
at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:480)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1070)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)
at org.apache.maven.wagon.providers.http.LightweightHttpWagon.finishPutTransfer(LightweightHttpWagon.java:185)
... 31 more
> [regression] deploy:deploy-file fails with secured repository
> -------------------------------------------------------------
>
> Key: MNG-4469
> URL: http://jira.codehaus.org/browse/MNG-4469
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0-alpha-5
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-6
>
>
> {{deploy:deploy-file}} or any other mojo that creates artifact repositories on its own will appear to ignore mirror, proxy and authentication infos from the settings when run with Maven 3.0. This is due to the {{ArtifactRepositoryFactory}} and the {{WagonManager}} being stateless and not injecting these infos any longer automatically.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-4469) [regression]
deploy:deploy-file fails with secured repository
Posted by "Asaf Mesika (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=270948#comment-270948 ]
Asaf Mesika edited comment on MNG-4469 at 6/21/11 6:02 AM:
-----------------------------------------------------------
Same error as Sarath with Maven 3.0.1
The authentication information is not used, as it is evident when watching the http network communication to nexus (tcpdump)
UPDATE: Sorry - I missed the next tcp conversations. It works. Password was wrong :)
was (Author: asafm):
Same error as Sarath with Maven 3.0.1
The authentication information is not used, as it is evident when watching the http network communication to nexus (tcpdump)
> [regression] deploy:deploy-file fails with secured repository
> -------------------------------------------------------------
>
> Key: MNG-4469
> URL: https://jira.codehaus.org/browse/MNG-4469
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0-alpha-5
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-6
>
>
> {{deploy:deploy-file}} or any other mojo that creates artifact repositories on its own will appear to ignore mirror, proxy and authentication infos from the settings when run with Maven 3.0. This is due to the {{ArtifactRepositoryFactory}} and the {{WagonManager}} being stateless and not injecting these infos any longer automatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4469) [regression] deploy:deploy-file fails
with secured repository
Posted by "Asaf Mesika (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=270948#comment-270948 ]
Asaf Mesika commented on MNG-4469:
----------------------------------
Same error as Sarath with Maven 3.0.1
The authentication information is not used, as it is evident when watching the http network communication to nexus (tcpdump)
> [regression] deploy:deploy-file fails with secured repository
> -------------------------------------------------------------
>
> Key: MNG-4469
> URL: http://jira.codehaus.org/browse/MNG-4469
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0-alpha-5
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-6
>
>
> {{deploy:deploy-file}} or any other mojo that creates artifact repositories on its own will appear to ignore mirror, proxy and authentication infos from the settings when run with Maven 3.0. This is due to the {{ArtifactRepositoryFactory}} and the {{WagonManager}} being stateless and not injecting these infos any longer automatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4469) [regression] deploy:deploy-file fails
with secured repository
Posted by "Stephan Weber (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208311#action_208311 ]
Stephan Weber commented on MNG-4469:
------------------------------------
(2010.01.27): just tried the new version of maven 3 alpha 6
mvn eclipse:to-maven -DdeployTo=man-uploads::default::http://leanserver.wdf.sap.corp:8081/nexus/content/repositories/man-uploads -DeclipseDir="C:\eclipse350"
still does only work if nexus security is switched off
> [regression] deploy:deploy-file fails with secured repository
> -------------------------------------------------------------
>
> Key: MNG-4469
> URL: http://jira.codehaus.org/browse/MNG-4469
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0-alpha-5
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-6
>
>
> {{deploy:deploy-file}} or any other mojo that creates artifact repositories on its own will appear to ignore mirror, proxy and authentication infos from the settings when run with Maven 3.0. This is due to the {{ArtifactRepositoryFactory}} and the {{WagonManager}} being stateless and not injecting these infos any longer automatically.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira