You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/10/30 15:29:26 UTC
[jira] Created: (MNG-4418) Dependency resolution appears to
misbehave if a remote repository uses the id "local"
Dependency resolution appears to misbehave if a remote repository uses the id "local"
-------------------------------------------------------------------------------------
Key: MNG-4418
URL: http://jira.codehaus.org/browse/MNG-4418
Project: Maven 2
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 2.2.1
Reporter: Benjamin Bentmann
Priority: Minor
Consider something like
{code:xml}
<mirror>
<id>local</id>
<mirrorOf>*</mirrorOf>
<url>http://localhost/mymirror</url>
</mirror>
{code}
in the settings. Note in particular that the mirror uses the id "local". This severely impacts dependency resolution as this repo id is internally used for the local repository. In particular the path to the locally stored repo metadata uses this id, i.e. {{maven-metadata-local.xml}}, making it impossible for Maven to distinguish the real local repo metadata from the remote repo called "local".
Possible error scenario:
- user installs local snapshot of a artifact A
- Maven checks remote repo "local" for updates of A, thereby overwriting {{maven-metadata-local.xml}} and erasing the information about the local snapshot
- Maven downloads snapshot version of A from the remote repo, regardless of its age compared to the locally installed snapshot
--
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] Closed: (MNG-4418) Dependency resolution appears to
misbehave if a remote repository uses the id "local"
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4418.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0-beta-1
Assignee: Benjamin Bentmann
Made model&settings validation error out if remote repository/mirror uses id "local" in [r929329|http://svn.apache.org/viewvc?view=revision&revision=929329].
> Dependency resolution appears to misbehave if a remote repository uses the id "local"
> -------------------------------------------------------------------------------------
>
> Key: MNG-4418
> URL: http://jira.codehaus.org/browse/MNG-4418
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Priority: Minor
> Fix For: 3.0-beta-1
>
>
> Consider something like
> {code:xml}
> <mirror>
> <id>local</id>
> <mirrorOf>*</mirrorOf>
> <url>http://localhost/mymirror</url>
> </mirror>
> {code}
> in the settings. Note in particular that the mirror uses the id "local". This severely impacts dependency resolution as this repo id is internally used for the local repository. In particular the path to the locally stored repo metadata uses this id, i.e. {{maven-metadata-local.xml}}, making it impossible for Maven to distinguish the real local repo metadata from the remote repo called "local".
> Possible error scenario:
> - user installs local snapshot of a artifact A
> - Maven checks remote repo "local" for updates of A, thereby overwriting {{maven-metadata-local.xml}} and erasing the information about the local snapshot
> - Maven downloads snapshot version of A from the remote repo, regardless of its age compared to the locally installed snapshot
--
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