Hello guys,
I'm running the tests in maven-archetype with Windows and a proxy (yeah, I
know :)) and one of them fails because it cannot find an archetype with the
archetype manager. So I looked at the DefaultDownloader in archetype-common
which injects ArtifactResolver like this:
@Requirement
private ArtifactResolver artifactResolver;
and when I stop with a breakpoint to inspect the artifact resolver, I see
it is of type DefaultArchetypeResolver and the WagonManager inside it has
an empty map of proxies defined. This however contradicts to my
settings.xml:
<proxies>
<proxy>
<id>aproxy</id>
<active>true</active>
<protocol>http</protocol>
<username></username>
<password></password>
<host>XXXX</host>
<port>XXXX</port>
<nonProxyHosts>localhost</nonProxyHosts>
</proxy>
</proxies>
Any idea who's defining the artifactResolver or why it does not respect my
settings.xml when running a test?
P.S. The build was failing because it couldn't download the dependencies,
but then I declared the proxy and that went fine. So it looks like the
proxy works fine when downloading dependencies, but not when I run the
tests.
--
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
