I think a problem I was having with this (see r682889) is that it then
doesn't honour the installation settings at all, since the value is
set by the ITs by reading settings.xml itself.
Not sure if that's really a big deal, as this is probably a more
valuable ability to have.
However just to note, I was thinking on the lines of having a tool to
create the sandboxed repo for you and having the verifier use that
(making all the settings redundant), rather than passing in one.
Cheers,
Brett
On 18/09/2008, at 1:33 AM, Benjamin Bentmann wrote:
Brett Porter wrote:
I really think that the entire suite should use a sandboxed local
repository
I just changed the maven-verifier to propagate the local repo of the
test runner to the IT build by default. Since "-D maven.repo.local"
is dominant over the settings.xml, this captures those ITs that use
a custom user settings, too.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
