[
https://jira.codehaus.org/browse/MNG-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=299897#comment-299897
]
Ondrej Zizka edited comment on MNG-5289 at 5/28/12 9:10 PM:
------------------------------------------------------------
Jason van Zyl:
{quote}
The artifacts have an identity. It matters where the artifacts were downloaded
from. Artifact A downloaded from X is not the same thing to Maven 3 as A
downloaded from Y. This can happen when you flip your settings.xml to go from
using a repository manager to using Maven Central directly for example.
There is currently no way to turn that off. But you can vote for the issue[1].
[1]: http://jira.codehaus.org/browse/MNG-5181
{quote}
http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html
was (Author: pekarna):
http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html
> -Dmaven.repo.local not honored
> ------------------------------
>
> Key: MNG-5289
> URL: https://jira.codehaus.org/browse/MNG-5289
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0.3
> Environment: Linux
> Reporter: Ondrej Zizka
>
> STR:
> 1) Checkout a multimodule project, e.g. JBoss AS 7
> {code}git clone git://github.com/jbossas/jboss-as.git{code}
> 2) {code}mvn -Dmaven.repo.local=foo dependencies:go-offline clean install
> -DallTests -DskipTests{code}
> 3) {code}mvn -Dmaven.repo.local=foo -o install -DallTests -DskipTests{code}
> This will complain about not having artifact XYZ.
> 4) On the other hand, this works:
> {code}
> mv ~/.m2/repository ~/.m2/repository_
> ln -s `pwd`/localRepo ~/.m2/repository
> mvn -o install
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
