The order is:
use system-properties if available,
otherwise use properties from pom.xml if available,
otherwise use properties from profiles.xml (only M2) if available,
otherwise use properties from user settings.xml if available,
otherwise use properties from global settings.xml
Is it possible t
It's not that easy. The corporate infrastructure only proxies central,
not any snapshot repos. So I can't test a Snapshot version.
So what I've done is verifying that the plugin now works with the new
embedded Maven 3 feature of Hudson. Really my main goal and should be
what I need for the corpora
Hi,
AFAIK no rush :-)
So take the time to test your various use cases.
2012/5/2 Anders Hammar :
>> If no settings specified, the maven invocation will use the default
>> one (~/.m2/settings.xml)
>
> Actually it will use the settings of the calling process, which could
> be something different than
> If no settings specified, the maven invocation will use the default
> one (~/.m2/settings.xml)
Actually it will use the settings of the calling process, which could
be something different than the default file-based one.
Due to corporate infrastructure reasons I couldn't test one of my
actual u
