Resolution: Won't Fix
Affects Version/s: 1.0-beta-6
Fix Version/s: None
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"
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.