# maven-issues mailing list archives

##### Site index · List index
Message view
Top
From "Arnaud Heritier (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (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:49:44 GMT

[ http://jira.codehaus.org/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174038#action_174038
]

Arnaud Heritier commented on MNG-4142:
--------------------------------------

Something else to add : If I launch after the site build, another build which doesn't produce
the main artefact (for example : mvn sonar), it will also fail trying to download dependency.
I think that it can be related to maven-metadata and more probably to the maven maven-metadata-local.xml
which is generated.
After the mvn site, I have in my local repository in org\apache\maven\it\test-metadata-local-clover\module1\1.0.0-SNAPSHOT:
{code}
module1-1.0.0-SNAPSHOT-clover.jar
module1-1.0.0-SNAPSHOT.pom
{code}
and in each metadata file :
{code}
<?xml version="1.0" encoding="UTF-8"?>
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<artifactId>module1</artifactId>
<version>1.0.0-SNAPSHOT</version>
{code}
{code}
<?xml version="1.0" encoding="UTF-8"?>
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<artifactId>module1</artifactId>
<version>1.0.0-SNAPSHOT</version>
<versioning>
<snapshot>
<localCopy>true</localCopy>
</snapshot>
<lastUpdated>20090423144418</lastUpdated>
</versioning>
{code}
{code}
<?xml version="1.0" encoding="UTF-8"?>
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<artifactId>module1</artifactId>
<version>1.0.0-SNAPSHOT</version>
<versioning>
<snapshot>
<timestamp>20090423.140624</timestamp>
<buildNumber>1</buildNumber>
</snapshot>
<lastUpdated>20090423140625</lastUpdated>
</versioning>
{code}
Do you think that maven-metadata-local.xml is good ? It says that there's a local copy whereas
there's no module1-1.0.0-SNAPSHOT.jar in the directory.

locally
> ---------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4142
>                 URL: http://jira.codehaus.org/browse/MNG-4142
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0.9, 2.0.10, 2.1.0
>         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 :
> {code}
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> Missing:
> ----------
>   Then, install it using the command:
-DartifactId=module1 -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/pa
> th/to/file
>   Alternatively, if you host your own repository you can deploy the file there:
-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 (http://maven-proxy.groupe.generali.fr/all),
> {code}
> It's anormal because I set a "local" remote repository in the build where it should try
> 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 occurs.
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-