Brett Porter wrote:
(see r682889)
Ah, and I was already wondering why the Hudson bundle ever (almost)
worked for me back in July.
it then
doesn't honour the installation settings at all, since the value is set
by the ITs by reading settings.xml itself.
What use case had you in mind about reading the installation settings?
The thing I am after with the change is keeping the IT sandbox intact.
In this context we have the following kind of builds:
1.) core-integration-tests-support
2.) core-integration-tests
3.) forked IT builds
a) using the default settings
b) using custom user settings
Due to the dependencies between these projects, we want all those builds
to use the same local repo. Now consider that builds 1.) and 2.) might
use a non-default location of the local repo, either by specifying
"maven.repo.local" or "--settings" on the comannd line. So we cannot
assume the IT builds will pick up the proper repo just by reading the
global/user settings.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
