Bernd,

your theory failed the test:

* Unplugged USB stick, so Maven has no passwords anymore
* Removed .m2\repository folder from disk, so Maven is enforced to download 
rather everything newly from our Nexus mirror
* "mvn clean package" built maven-dependency-plugin without any problem

Conclusion: It is definitively NOT a download problem, but still supports my 
theory that maven-dependency-plugin wants to UPLOAD something at "package" 
phase.

If I just would have kept the protocol earlier today, I could tell you what 
"thing" actually it was... :-(

Regards
-Markus


-----Ursprüngliche Nachricht-----
Von: Bernd [mailto:[email protected]] 
Gesendet: Mittwoch, 18. März 2015 14:27
An: Maven Users List
Betreff: Re: "mvn clean package" requests access rights for local Nexus 
repository

Hello,

It sounds more like a download as it does not ask again. You can wipe your 
local repo cache (or use a different one in settings.xml) and try to reproduce 
the problem. If you run with -X and actually keep the maven log output you 
should be able to see the access in question.

Gruss
Bernd
Am 18.03.2015 14:02 schrieb "Markus Karg" <[email protected]>:

> Dear Maven Experts,
>
> just did "svn checkout" to get trunk of maven-dependency-plugin, and 
> wanted to build it using "mvn clean package". What then happened is 
> really
> scary:
>
>
> *         It complained about missing access on that path where my USB
> stick stores the encrypted password for my local Nexus repository.
>
> *         My local Nexus repository is a mirror of "central" with public
> access, only demanding passwords for uploads.
>
> *         I plugged in my stick, did "mvn clean package" again, and it
> worked pretty well.
>
> *         REMOVED my stick, and since then "mvn clean package" works
> without, still!
>
> That looks if packaging "maven-dependency-plugin" would need to WRITE 
> into my Nexus (possibly central?) at package phase, if a particular 
> "thing" is not found there.
>
> This is scary, as nobody expects UPLOADS are done at packaging.
>
> If somebody has an explanation why that happens, I'd ask him to 
> publish here, so everybody will understand the reason for this! :)
>
> Regards
> -Markus
>
>
>

Reply via email to