Brett Porter wrote:
I think this is no longer an issue as long as settings.xml used "external:*" instead of just "*", which I think is a good enough requirement for the ITs
An IT should be as independent from the outside environment as possible, i.e. if I can tweak the IT to pass regardless of the installation settings used by the executing Maven, I believe that's worth to go for.
Even when using -s settings.xml, if the definitions is in the Maven installation's settings.xml it'll be applied as -s only overrides the ~/.m2/*
The project description for the IT says:
Test for repository inheritence - ensure using the same id overrides the defaults
AFAIU, this means the IT is only concerned about the effective POM (and indeed was previously using help:effective-pom to check) and not the effective URL that Maven ultimatively picks at runtime to access the repo. As such, mirror settings should be irrelevant here. And since user settings override global settings, the added settings.xml will successfully update the effective POM.
Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
