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 2008/07/28 15:50:40 UTC
[jira] Updated: (MINVOKER-43) Sync repository identifier of custom
IT repo with identifier of real local repository
[ http://jira.codehaus.org/browse/MINVOKER-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MINVOKER-43:
--------------------------------------
Priority: Major (was: Minor)
Description:
If the user specifies a custom location for the IT repo, the plugin is currently using the identifier "it-repo" for this repository. However, the real local repo has the identifier "local". As a result, the metadata files created for the staged artifacts have a wrong file name, i.e. {{maven-metadata-it-repo.xml}} instead of {{maven-metadata-local.xml}} as expected by Maven for a local repository.
This gives rise to odd test failures: When the IT builds run, Maven will (expectedly) ignore the badly named metadata files. Since the local repo metadata can't be found, Maven will then query the remote repos for updates of the artifacts under test. This in turn can make Maven use out-dated snapshots and *not* the artifact versions that have just been built locally.
was:If the user specified a custom location for the IT repo, the plugin is currently using the identifier "it-repo" for this repository. However, the real local repo has the identifier "local". This makes it in principal possible for a component under test to tell these repositories apart, potentially causing different behavior during integration testing than in real world. For example, the repository identifier is used in construction of the repository metadata files, e.g. {{maven-metadata-local.xml}}.
Issue Type: Bug (was: Improvement)
> Sync repository identifier of custom IT repo with identifier of real local repository
> -------------------------------------------------------------------------------------
>
> Key: MINVOKER-43
> URL: http://jira.codehaus.org/browse/MINVOKER-43
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 1.3
>
>
> If the user specifies a custom location for the IT repo, the plugin is currently using the identifier "it-repo" for this repository. However, the real local repo has the identifier "local". As a result, the metadata files created for the staged artifacts have a wrong file name, i.e. {{maven-metadata-it-repo.xml}} instead of {{maven-metadata-local.xml}} as expected by Maven for a local repository.
> This gives rise to odd test failures: When the IT builds run, Maven will (expectedly) ignore the badly named metadata files. Since the local repo metadata can't be found, Maven will then query the remote repos for updates of the artifacts under test. This in turn can make Maven use out-dated snapshots and *not* the artifact versions that have just been built locally.
--
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