[
https://jira.codehaus.org/browse/WAGON-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed WAGON-291.
--------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> Maven uses artifact download credentials during deployment in some
> circumstances
> --------------------------------------------------------------------------------
>
> Key: WAGON-291
> URL: https://jira.codehaus.org/browse/WAGON-291
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http-lightweight
> Affects Versions: 1.0-beta-6
> Reporter: Richard Seddon
>
> If Maven downloads an artifact using authorization, this authorization seems
> to be cached, which can cause a subsequent deployment to succeed where it
> should have failed.
> Steps to reproduce:
> # Set up a build which will require downloading an artifact from a Nexus
> server which requires authentication, and configure your settings.xml
> appropriately.
> # Create a project with a distribution management section which points to a
> repository in the above server. Make sure the repository id doesn't exist in
> your settings.xml
> # Run "mvn deploy"
> What happens:
> If the credentials used to download artifacts from Nexus have deployment
> privileges in the Nexus repository the deployment will succeed.
> Now run "mvn deploy" again. This time the deployment will fail with a 401
> code.
> This bug exists in both Maven 2.2.1 and the latest Maven 3.0 snapshots.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
