2009/6/10 Nick Stolwijk <[email protected]> > [quote] > But there seems to be no way to get also Ex3 into that folder, because the > dependency:tree-output doesn't even list Ex3. > [/quote] > > Because of this piece I think there is something wrong with the pom > file of your Z artifact. Can you take a look in your local repository > in the pom file of Z to see if the dependency is really compile? It > shouldn't matter in which repo an artifact lives. >
Unless the artifact is a -SNAPSHOT artifact and you are pulling from a repository with releases set to false... I'll dig up the code... somebody helpfully found this strange bug in Maven's core (found by the versions-maven-plugin) http://jira.codehaus.org/browse/MVERSIONS-19 essentially, if you have <repository> <id>my-snapshot-repository</id> <name>My Snapshot Repository</name> <url>http://my.repo/snapshot</url> <releases> <enabled>false</enabled> </releases> </repository> Then this method: http://maven.apache.org/ref/current/xref/org/apache/maven/project/artifact/MavenMetadataSource.html#495 This method creates a RepositoryMetadata object of type: http://maven.apache.org/ref/current/xref/org/apache/maven/artifact/repository/metadata/ArtifactRepositoryMetadata.html#31 This metadata object is passed to the RepositoryMetadataManager: http://maven.apache.org/ref/current/xref/org/apache/maven/artifact/repository/metadata/DefaultRepositoryMetadataManager.html#58 Which asks the RepositoryMetadata object if it is a snapshot... http://maven.apache.org/ref/current/xref/org/apache/maven/artifact/repository/metadata/DefaultRepositoryMetadataManager.html#69 but our metadata object can never be a snapshot: http://maven.apache.org/ref/current/xref/org/apache/maven/artifact/repository/metadata/ArtifactRepositoryMetadata.html#81 So the end result is that we never look in non-release repositories... not sure if this is a Maven bug or if we should be using a different method. I tried getting one of the Maven developers to look into it, but had no luck... I am also not sure of the implications of changing the existing behaviour w.r.t. updating the metadata that these functions seem to imply will get updated. > > Hth, > > Nick Stolwijk > ~Java Developer~ > > Iprofs BV. > Claus Sluterweg 125 > 2012 WS Haarlem > www.iprofs.nl > > > > On Wed, Jun 10, 2009 at 3:36 PM, gorgophol<[email protected]> wrote: > > > > Thanks for your fast reply. > > > > Scope for all dependencies is "compile". > > In none of those POMs any <scope>-tag is used. It's all maven-standard > > (compile). > > > > If any scope was "provided" or so, I would understand that it isn't > copied. > > But all other dependencies are copied. > > > > So I thought it might be because Z is in Repos2. > > But that should be no problem in my opinion. > > -- > > View this message in context: > http://www.nabble.com/maven-dependency-plugin-doesn%27t-find-all-dependencies-in-several-repositories-tp23961970p23962522.html > > Sent from the Maven - Users mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > 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] > >
