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
