Yes, I tried that. First, a wipe of just our artifacts (from the local
repository) then a complete wipe(from the local repository). After both
wipes, the artifact was still trying to get pulled down.
Entner Harald wrote:
Have you tried to delete the complete repository (.../.m2/repository), in which the false artifact is found? Maybe there are some legacy artifacts in it, which in return have dependencies on others and so on.
-----Ursprüngliche Nachricht-----
Von: Michael Delaney [mailto:[email protected]]
Gesendet: Montag, 5. Oktober 2009 16:56
An: [email protected]
Betreff: Showing pom files in dependency tree.
All,
I'm trying to diagnose an odd problem. The problem is on *some*, but not
all, machines, one of our projects is trying to download an old retired
snapshot build. I can't reproduce this locally but I can on our CI
server. I checked the pom (top-level and parents) and check for this
reference and it isn't there. I'm trying to figure out how this jar is
being included when it shouldn't and I thought being able to see exactly
what pom files are being loaded in would help.
I already tried using the dependency plug-in to list the pom files but
that doesn't work. I even searched through our Archiva repository for
references and couldn't find anything that could cause this.
Anyone have any ideas?
---------------------------------------------------------------------
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]
