maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arnaud Heritier (JIRA)" <>
Subject [jira] Created: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally
Date Thu, 23 Apr 2009 14:29:45 GMT
Maven doesn't try to download a dependency when it already exists a version with classifier

                 Key: MNG-4142
             Project: Maven 2
          Issue Type: Bug
          Components: Dependencies
    Affects Versions: 2.1.0, 2.0.10, 2.0.9
         Environment: Java 5, Windows XP
            Reporter: Arnaud Heritier
            Priority: Critical

When maven installs in the local repository an artifact with a classifier, and not the principal
artifact, it won't try in a reactor to download the principal artifact from the remote repository.
I created a testcase to reproduce it. It's quite simple. You unzip it and in the root directory
you launch {code}mvn site{code}
This build uses clover, thus it installs locally cloverified versions of artifacts.
The build will fail because it doesn't find the SNAPSHOT of the module1 :
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.


  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DartifactId=module1
-Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/pa

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DartifactId=module1
-Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path
/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:

1 required artifact is missing.

for artifact:

from the specified remote repositories:
  central (,
  remote-repo (file://E:\jtb\workspaces\tests\test-metadata-local-clover/remote-repo)
It's anormal because I set a "local" remote repository in the build where it should try to
download it.
You can validate that it is working by launching :
{code}mvn install -f module2/pom.xml{code}

This bug is really annoying for us. It exists for a long long time now. I thought it was due
to a problem with metadata sent by archiva, but after migrating to nexus the problem always
I don't know if the problem is in metadata or in the reactor itself. I think it is the second
one. There are many issues opened about the reactor and classifiers.
Is there some who can try if it can reproduce the error with my testcase ?
It should be easy to create a real IT for maven with it if it is necessary.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message