Is it possible that the dependency-plugin uses information from localRepository instead of Repos 1 and 2?
I recognized the follwoing behavior: Every time I install an artifact into Repos 2 using deploy:file, the jar and the pom.xml are installed into correctly into Repos 2 (with all the correct dependency-entries in the pom.xml). but also the pom.xml of the artifact in my localRepository is replaced with a new one, containing no dependecies ... Just for explanation: Artifact Z is built by another group and deployed in their own repository using deploy-phase. Maven also installs it in localRepository in the install-phase. If tests are ok, Artifact Z (and pom.xml) are deployed into Repos 2, where other groups also may use it as dependency. As described above, this seems to kill the pom.xml in localRepository. May be a bug in deploy-plugin? But dependency-plugin shouldn't use any information stored in localRepositories in my oppinion! -- View this message in context: http://www.nabble.com/maven-dependency-plugin-doesn%27t-find-all-dependencies-in-several-repositories-tp23961970p24034808.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
