[ http://jira.codehaus.org/browse/MINVOKER-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143353#action_143353 ]
Benjamin Bentmann commented on MINVOKER-43: ------------------------------------------- Possible workaround (at least for single module builds): Instead of {{invoker:install}}, use the {{install:install-file}} goal and be sure to set its [localRepositoryId|http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html#localRepositoryId] parameter to "local". > 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