subject:"\[jira\] \[Commented\] \(MNG\-4142\) Maven doesn't try to download a dependency when it already exists a version with classifier locally"

[jira] [Commented] (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2020-11-21 Thread Michael Osipov (Jira)



[ 
https://issues.apache.org/jira/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17236797#comment-17236797
 ] 

Michael Osipov commented on MNG-4142:
-

I am still waiting for a new, proper sample project...

> Maven doesn't try to download a dependency when it already exists a version 
> with classifier locally
> ---
>
> Key: MNG-4142
> URL: https://issues.apache.org/jira/browse/MNG-4142
> Project: Maven
>  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
> Fix For: waiting-for-feedback
>
> Attachments: MNG-4142.patch, test-metadata-local-clover.zip
>
>
> 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:
> --
> 1) org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
>   mvn install:install-file 
> -DgroupId=org.apache.maven.it.test-metadata-local-clover -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:
>   mvn deploy:deploy-file 
> -DgroupId=org.apache.maven.it.test-metadata-local-clover -DartifactId=module1 
> -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path
> /to/file -Durl=[url] -DrepositoryId=[id]
>   Path to dependency:
> 1) 
> org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
> 2) 
> org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
> --
> 1 required artifact is missing.
> for artifact:
>   org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
> from the specified remote repositories:
>   central (http://maven-proxy.groupe.generali.fr/all),
>   remote-repo 
> (file://E:\jtb\workspaces\tests\test-metadata-local-clover/remote-repo)
> {code}
> 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 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 was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2020-03-12 Thread Michael Osipov (Jira)



[ 
https://issues.apache.org/jira/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057694#comment-17057694
 ] 

Michael Osipov commented on MNG-4142:
-

It may take a day or two to debug this :-(

> Maven doesn't try to download a dependency when it already exists a version 
> with classifier locally
> ---
>
> Key: MNG-4142
> URL: https://issues.apache.org/jira/browse/MNG-4142
> Project: Maven
>  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
> Attachments: MNG-4142.patch, test-metadata-local-clover.zip
>
>
> 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:
> --
> 1) org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
>   mvn install:install-file 
> -DgroupId=org.apache.maven.it.test-metadata-local-clover -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:
>   mvn deploy:deploy-file 
> -DgroupId=org.apache.maven.it.test-metadata-local-clover -DartifactId=module1 
> -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path
> /to/file -Durl=[url] -DrepositoryId=[id]
>   Path to dependency:
> 1) 
> org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
> 2) 
> org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
> --
> 1 required artifact is missing.
> for artifact:
>   org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
> from the specified remote repositories:
>   central (http://maven-proxy.groupe.generali.fr/all),
>   remote-repo 
> (file://E:\jtb\workspaces\tests\test-metadata-local-clover/remote-repo)
> {code}
> 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 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 was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2020-03-12 Thread Ryabokon Roman (Jira)



[ 
https://issues.apache.org/jira/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057641#comment-17057641
 ] 

Ryabokon Roman commented on MNG-4142:
-

maven 3.6.1 This issue still persists :(

I spent about 2 weeks searching for the problem, discovered by accident. The 
problem is the same, only we do not have a snapshot, but a release

> Maven doesn't try to download a dependency when it already exists a version 
> with classifier locally
> ---
>
> Key: MNG-4142
> URL: https://issues.apache.org/jira/browse/MNG-4142
> Project: Maven
>  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
> Attachments: MNG-4142.patch, test-metadata-local-clover.zip
>
>
> 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:
> --
> 1) org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
>   mvn install:install-file 
> -DgroupId=org.apache.maven.it.test-metadata-local-clover -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:
>   mvn deploy:deploy-file 
> -DgroupId=org.apache.maven.it.test-metadata-local-clover -DartifactId=module1 
> -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path
> /to/file -Durl=[url] -DrepositoryId=[id]
>   Path to dependency:
> 1) 
> org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
> 2) 
> org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
> --
> 1 required artifact is missing.
> for artifact:
>   org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
> from the specified remote repositories:
>   central (http://maven-proxy.groupe.generali.fr/all),
>   remote-repo 
> (file://E:\jtb\workspaces\tests\test-metadata-local-clover/remote-repo)
> {code}
> 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 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 was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2019-12-16 Thread Elliotte Rusty Harold (Jira)



[ 
https://issues.apache.org/jira/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997263#comment-16997263
 ] 

Elliotte Rusty Harold commented on MNG-4142:


Poor description, but I've seen this myself. 

> Maven doesn't try to download a dependency when it already exists a version 
> with classifier locally
> ---
>
> Key: MNG-4142
> URL: https://issues.apache.org/jira/browse/MNG-4142
> Project: Maven
>  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
> Attachments: MNG-4142.patch, test-metadata-local-clover.zip
>
>
> 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:
> --
> 1) org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
>   mvn install:install-file 
> -DgroupId=org.apache.maven.it.test-metadata-local-clover -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:
>   mvn deploy:deploy-file 
> -DgroupId=org.apache.maven.it.test-metadata-local-clover -DartifactId=module1 
> -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path
> /to/file -Durl=[url] -DrepositoryId=[id]
>   Path to dependency:
> 1) 
> org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
> 2) 
> org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
> --
> 1 required artifact is missing.
> for artifact:
>   org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
> from the specified remote repositories:
>   central (http://maven-proxy.groupe.generali.fr/all),
>   remote-repo 
> (file://E:\jtb\workspaces\tests\test-metadata-local-clover/remote-repo)
> {code}
> 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 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 was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2016-10-15 Thread Michael Osipov (JIRA)


[ 
https://issues.apache.org/jira/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15578902#comment-15578902
 ] 

Michael Osipov commented on MNG-4142:
-

Perfectly fine usecase and I am convinced that this works. See post below.

> Maven doesn't try to download a dependency when it already exists a version 
> with classifier locally
> ---
>
> Key: MNG-4142
> URL: https://issues.apache.org/jira/browse/MNG-4142
> Project: Maven
>  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
> Attachments: MNG-4142.patch, test-metadata-local-clover.zip
>
>
> 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:
> --
> 1) org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
>   mvn install:install-file 
> -DgroupId=org.apache.maven.it.test-metadata-local-clover -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:
>   mvn deploy:deploy-file 
> -DgroupId=org.apache.maven.it.test-metadata-local-clover -DartifactId=module1 
> -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path
> /to/file -Durl=[url] -DrepositoryId=[id]
>   Path to dependency:
> 1) 
> org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
> 2) 
> org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
> --
> 1 required artifact is missing.
> for artifact:
>   org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
> from the specified remote repositories:
>   central (http://maven-proxy.groupe.generali.fr/all),
>   remote-repo 
> (file://E:\jtb\workspaces\tests\test-metadata-local-clover/remote-repo)
> {code}
> 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 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 was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2016-10-15 Thread Michael Osipov (JIRA)


[ 
https://issues.apache.org/jira/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15578899#comment-15578899
 ] 

Michael Osipov commented on MNG-4142:
-

I need to revert my previous statement partially. I have found probably the 
issue why this is caused. Initially I thought that this is MNG-4343, but it 
isn't. It is the Clover Maven Plugin. First of all, I have updated to 4.1.2 to 
reproduce with the attached usecase. The issue is located as well as in the 
plugin but also in the sample project configuration. At runtime clover replaces 
the main artifact with a classified one. This happens in {{pre-site}} phase. 
Unfortunately, the author of the sample project added {{module1}} as a 
dependency of {{module2}}, but forgot to add the classifier. If you now run 
with added classifier, the stuff works. It can never ever work the way it is 
configured now because there is no unclassified main artifact to depend upon 
due to Clover plugin.

Upshot: this is a misconfiguration in your POMs.

If some one now still thinks that this will fail even if a main and a side 
artifact exist, please create a proper sample project.

> Maven doesn't try to download a dependency when it already exists a version 
> with classifier locally
> ---
>
> Key: MNG-4142
> URL: https://issues.apache.org/jira/browse/MNG-4142
> Project: Maven
>  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
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: MNG-4142.patch, test-metadata-local-clover.zip
>
>
> 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:
> --
> 1) org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
>   mvn install:install-file 
> -DgroupId=org.apache.maven.it.test-metadata-local-clover -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:
>   mvn deploy:deploy-file 
> -DgroupId=org.apache.maven.it.test-metadata-local-clover -DartifactId=module1 
> -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path
> /to/file -Durl=[url] -DrepositoryId=[id]
>   Path to dependency:
> 1) 
> org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
> 2) 
> org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
> --
> 1 required artifact is missing.
> for artifact:
>   org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
> from the specified remote repositories:
>   central (http://maven-proxy.groupe.generali.fr/all),
>   remote-repo 
> (file://E:\jtb\workspaces\tests\test-metadata-local-clover/remote-repo)
> {code}
> 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 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 was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2011-07-14 Thread nodje (JIRA)

[
https://jira.codehaus.org/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273210#comment-273210
]

nodje commented on MNG-4142:

I've the same problem but with standard SNAPSHOT dependencies, not using
classifier, and with 3.0.3.

Maven doesn't try to download a dependency when it already exists a version
with classifier locally
---

Key: MNG-4142
URL: https://jira.codehaus.org/browse/MNG-4142
Project: Maven 2 3
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
Fix For: Issues to be reviewed for 3.x

Attachments: MNG-4142.patch, test-metadata-local-clover.zip

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:
--
1) org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file
-DgroupId=org.apache.maven.it.test-metadata-local-clover -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:
mvn deploy:deploy-file
-DgroupId=org.apache.maven.it.test-metadata-local-clover -DartifactId=module1
-Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path
/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1)
org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
2)
org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
--
1 required artifact is missing.
for artifact:
org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
from the specified remote repositories:
central (http://maven-proxy.groupe.generali.fr/all),
remote-repo
(file://E:\jtb\workspaces\tests\test-metadata-local-clover/remote-repo)
{code}
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 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2011-07-14 Thread Martin Todorov (JIRA)

[
https://jira.codehaus.org/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273211#comment-273211
]

Martin Todorov commented on MNG-4142:
-

This bug/feature doesn't really have much to do with classifiers. I believe the
original bug report filer just thought it had something to do with the problem.
Perhaps somebody should rename the bug to Maven doesn't try to download
SNAPSHOT artifacts, if you've installed them locally; even if you pass -U.

I believe that by using -U the local metadata should get unlocked for the
locally installed SNAPSHOT artifacts.

Maven doesn't try to download a dependency when it already exists a version
with classifier locally
---

Attachments: MNG-4142.patch, test-metadata-local-clover.zip

[ERROR] BUILD ERROR
[INFO]

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2011-07-14 Thread nodje (JIRA)

[
https://jira.codehaus.org/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273213#comment-273213
]

nodje commented on MNG-4142:

alright, good then, that's my problem!

Can't wait for the fix to come, hopefully as early as 3.0.4...

Maven doesn't try to download a dependency when it already exists a version
with classifier locally
---

Attachments: MNG-4142.patch, test-metadata-local-clover.zip

[ERROR] BUILD ERROR
[INFO]

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2010-10-28 Thread Martin Todorov (JIRA)

[
http://jira.codehaus.org/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=241305#action_241305
]

Martin Todorov commented on MNG-4142:
-

Bonjour Arnaud!

As per your request, I have tested this with Maven 3.0 today. I am afraid the
problem still persists. Today this actually happened with a completely
different project/setup/machine under both Maven 2.2.1 and 3.0.

This is not just annoying, it's actually a show-stopper when it happens to a
developer who's not expecting it, as they spend quite some time trying to
figure it out.

Please review for the release of Maven 3.1, (if a 2.x version will not be
further released).

Regards,

Martin

Maven doesn't try to download a dependency when it already exists a version
with classifier locally
---

Key: MNG-4142
URL: http://jira.codehaus.org/browse/MNG-4142
Project: Maven 2 3
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
Fix For: Issues to be reviewed for 3.x

Attachments: MNG-4142.patch, test-metadata-local-clover.zip

[ERROR] BUILD ERROR
[INFO]

--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2010-10-27 Thread Martin Todorov (JIRA)

[
http://jira.codehaus.org/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=241160#action_241160
]

Martin Todorov commented on MNG-4142:
-

Hi,

I would like to ask why the attached patch is not being accepted?
There are currently over three dozen votes for this and it is apparent that
people are hitting the problem.

In addition, perhaps the title of the bug is not quite correct. This doesn't
just happen for artifacts with classifiers. In our case it happens for POM
files where there are several inherited POMs.
We're using Hudson and Nexus had to limit the parents to build on one Hudson
node, while all modules which depend on them - on the rest of the nodes.

I also think this is a huge and very obscure problem (esp. with distributed
builds) and, provided that there is already a patch, I believe it's about time
for it to be reviewed.

Regards,

Martin

Maven doesn't try to download a dependency when it already exists a version
with classifier locally
---

Attachments: MNG-4142.patch, test-metadata-local-clover.zip

[ERROR] BUILD ERROR
[INFO]

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2010-10-27 Thread Arnaud Heritier (JIRA)

[
http://jira.codehaus.org/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=241162#action_241162
]

Arnaud Heritier commented on MNG-4142:
--

Were you able to test if the problem exists with maven 3 ?
I agree that this issue is really annoying but for now there is no 2.X version
release scheduled.
That's why there was no feedback from dev team.

Maven doesn't try to download a dependency when it already exists a version
with classifier locally
---

Attachments: MNG-4142.patch, test-metadata-local-clover.zip

[ERROR] BUILD ERROR
[INFO]

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2010-05-31 Thread Brian Laframboise (JIRA)

[
http://jira.codehaus.org/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=223246#action_223246
]

Brian Laframboise commented on MNG-4142:

I just ran into this issue myself. A build on one of my build machines was
failing due to maven not downloading a newer version of a dependency that was
available on Nexus because it had previously installed an earlier version of
that same dependency into the local repository.

When I removed the localCopytrue/localCopy element from the metadata of the
non-updating dependency the problem went away - and dutifully came back when I
re-added it.

Peter, I agree - this is a scary problem for anybody trying to implement a
distributed build system. What I don't understand is why more people are not
encountering this issue.

For now I'll attempt a workaround this by adding a cron job, per build agent,
to frequently change localCopy back to false. If anybody has a better
suggestion, I'd love to hear it.

Maven doesn't try to download a dependency when it already exists a version
with classifier locally
---

Attachments: MNG-4142.patch, test-metadata-local-clover.zip

[ERROR] BUILD ERROR
[INFO]

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2009-11-30 Thread Peter Liljenberg (JIRA)


[ 
http://jira.codehaus.org/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=199976#action_199976
 ] 

Peter Liljenberg commented on MNG-4142:
---

I've encountered this problem as well when doing distributed builds (using 
Hudson).
When one build server (#1) builds and deploys an artifact the 
maven-metadata-local.xml will contain the localCopy attribute:
  versioning
snapshot
  localCopytrue/localCopy
/snapshot
lastUpdated20091127124227/lastUpdated
  /versioning

Which means that if another build server builds the same module AFTER server #1 
and produce a new artifact in the repository, machine #1 will never download 
this new SNAPSHOT version when trying to build artifacts depending on the 
artifact.
This is a huge problem (and a scary one!) for us and I would like to see a fix 
for this soon :)

 Maven doesn't try to download a dependency when it already exists a version 
 with classifier 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
 Fix For: 2.2.x

 Attachments: MNG-4142.patch, test-metadata-local-clover.zip


 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:
 --
 1) org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
   Try downloading the file manually from the project website.
   Then, install it using the command:
   mvn install:install-file 
 -DgroupId=org.apache.maven.it.test-metadata-local-clover -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:
   mvn deploy:deploy-file 
 -DgroupId=org.apache.maven.it.test-metadata-local-clover -DartifactId=module1 
 -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path
 /to/file -Durl=[url] -DrepositoryId=[id]
   Path to dependency:
 1) 
 org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
 2) 
 org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
 --
 1 required artifact is missing.
 for artifact:
   org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
 from the specified remote repositories:
   central (http://maven-proxy.groupe.generali.fr/all),
   remote-repo 
 (file://E:\jtb\workspaces\tests\test-metadata-local-clover/remote-repo)
 {code}
 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 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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2009-08-18 Thread David Rousselie (JIRA)


[ 
http://jira.codehaus.org/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=187470#action_187470
 ] 

David Rousselie commented on MNG-4142:
--

The problem is that when the Maven resolve the artifact version with 
maven-metadata-local.xml when it exists and it resolves it to 1.0.0-SNAPSHOT 
whereas only module1-1.0.0-SNAPSHOT-clover.jar (in this exemple). Then when it 
try to access the file artifact (module1-1.0.0-SNAPSHOT.jar) and fails, it 
tries to get the *same version* on remote repositories whereas it should have 
try to resolve the artifact version with data found in 
maven-metadata-${remotereponame}.xml before trying to get it from each 
repository.

I have attached a small patch (base on revision 805295 in branch maven-2.2.x) 
which might not be the best way to correct this bug : while resolving artifact 
version, it loads local metadata only if artifact's file exists locally.

 Maven doesn't try to download a dependency when it already exists a version 
 with classifier 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
 Fix For: 2.2.x

 Attachments: test-metadata-local-clover.zip


 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:
 --
 1) org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
   Try downloading the file manually from the project website.
   Then, install it using the command:
   mvn install:install-file 
 -DgroupId=org.apache.maven.it.test-metadata-local-clover -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:
   mvn deploy:deploy-file 
 -DgroupId=org.apache.maven.it.test-metadata-local-clover -DartifactId=module1 
 -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path
 /to/file -Durl=[url] -DrepositoryId=[id]
   Path to dependency:
 1) 
 org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
 2) 
 org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
 --
 1 required artifact is missing.
 for artifact:
   org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
 from the specified remote repositories:
   central (http://maven-proxy.groupe.generali.fr/all),
   remote-repo 
 (file://E:\jtb\workspaces\tests\test-metadata-local-clover/remote-repo)
 {code}
 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 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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

2009-04-23 Thread Arnaud Heritier (JIRA)


[ 
http://jira.codehaus.org/browse/MNG-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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}
maven-metadata-central.xml
maven-metadata-local.xml
maven-metadata-remote-repo.xml
maven-metadata-remote-repo.xml.sha1
module1-1.0.0-SNAPSHOT-clover.jar
module1-1.0.0-SNAPSHOT.pom
{code}
and in each metadata file :
* maven-metadata-central.xml
{code}
?xml version=1.0 encoding=UTF-8?
metadata xsi:schemaLocation=http://maven.apache.org/METADATA/1.0.0 
http://maven.apache.org/xsd/metadata-1.0.0.xsd; 
xmlns=http://maven.apache.org/METADATA/1.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  groupIdorg.apache.maven.it.test-metadata-local-clover/groupId
  artifactIdmodule1/artifactId
  version1.0.0-SNAPSHOT/version
/metadata
{code}
* maven-metadata-local.xml
{code}
?xml version=1.0 encoding=UTF-8?
metadata xsi:schemaLocation=http://maven.apache.org/METADATA/1.0.0 
http://maven.apache.org/xsd/metadata-1.0.0.xsd; 
xmlns=http://maven.apache.org/METADATA/1.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  groupIdorg.apache.maven.it.test-metadata-local-clover/groupId
  artifactIdmodule1/artifactId
  version1.0.0-SNAPSHOT/version
  versioning
snapshot
  localCopytrue/localCopy
/snapshot
lastUpdated20090423144418/lastUpdated
  /versioning
/metadata
{code}
* maven-metadata-remote-repo.xml
{code}
?xml version=1.0 encoding=UTF-8?
metadata xsi:schemaLocation=http://maven.apache.org/METADATA/1.0.0 
http://maven.apache.org/xsd/metadata-1.0.0.xsd; 
xmlns=http://maven.apache.org/METADATA/1.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  groupIdorg.apache.maven.it.test-metadata-local-clover/groupId
  artifactIdmodule1/artifactId
  version1.0.0-SNAPSHOT/version
  versioning
snapshot
  timestamp20090423.140624/timestamp
  buildNumber1/buildNumber
/snapshot
lastUpdated20090423140625/lastUpdated
  /versioning
/metadata
{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.




 Maven doesn't try to download a dependency when it already exists a version 
 with classifier 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
 Attachments: test-metadata-local-clover.zip


 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:
 --
 1) org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
   Try downloading the file manually from the project website.
   Then, install it using the command:
   mvn install:install-file 
 -DgroupId=org.apache.maven.it.test-metadata-local-clover -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:
   mvn deploy:deploy-file 
 -DgroupId=org.apache.maven.it.test-metadata-local-clover -DartifactId=module1 
 -Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path
 /to/file -Durl=[url] -DrepositoryId=[id]
   Path to dependency:
 1) 
 org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
 2) 
 org.apache.maven.it.test-metadata-local-clover:module1:jar:1.0.0-SNAPSHOT
 --
 1 required artifact is missing.
 for artifact:
   org.apache.maven.it.test-metadata-local-clover:module2:jar:1.0.0-SNAPSHOT
 from the

[jira] [Commented] (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

[jira] [Commented] (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

[jira] [Commented] (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

[jira] [Commented] (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

[jira] [Commented] (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

[jira] [Commented] (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

[jira] Commented: (MNG-4142) Maven doesn't try to download a dependency when it already exists a version with classifier locally

16 matches

Site Navigation

Mail list logo

Footer information