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/08/09 20:24:26 UTC
[jira] Created: (MINVOKER-47) Test builds fail to locate staged
artifacts when using custom settings and non-default local repo path
Test builds fail to locate staged artifacts when using custom settings and non-default local repo path
------------------------------------------------------------------------------------------------------
Key: MINVOKER-47
URL: http://jira.codehaus.org/browse/MINVOKER-47
Project: Maven 2.x Invoker Plugin
Issue Type: Bug
Affects Versions: 1.2
Reporter: Benjamin Bentmann
Priority: Minor
If the {{invoker:run}} goal
- is configured to use a custom user settings file (as recommended for fast builds)
- and no isolated local repo is to be used (not recommended but possible)
- and the user has customized the location of his local repo
the IT builds will fail.
The {{invoker:install}} will properly stage the artifacts into the user's local repo but using a custom IT settings files (which doesn't specify a local repo path) will make Maven use the default local repo, which is empty.
Hence, we should always specify the local repo path for the Maven invocation and not rely on Maven fetching it from the settings.
--
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: (MINVOKER-47) Test builds fail to locate staged
artifacts when using custom settings and non-default local repo path
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MINVOKER-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MINVOKER-47.
-------------------------------------
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 1.3
Fixed in [r684345|http://svn.apache.org/viewvc?view=rev&revision=684345].
> Test builds fail to locate staged artifacts when using custom settings and non-default local repo path
> ------------------------------------------------------------------------------------------------------
>
> Key: MINVOKER-47
> URL: http://jira.codehaus.org/browse/MINVOKER-47
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Priority: Minor
> Fix For: 1.3
>
>
> If the {{invoker:run}} goal
> - is configured to use a custom user settings file (as recommended for fast builds)
> - and no isolated local repo is to be used (not recommended but possible)
> - and the user has customized the location of his local repo
> the IT builds will fail.
> The {{invoker:install}} will properly stage the artifacts into the user's local repo but using a custom IT settings files (which doesn't specify a local repo path) will make Maven use the default local repo, which is empty.
> Hence, we should always specify the local repo path for the Maven invocation and not rely on Maven fetching it from the settings.
--
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