Try removing the http:
maven.proxy.nonProxyHosts=192.168.0.54
And would you share how you made the tomcat plugin work? Maybe other
users could still profit from it. :)
Thanks,
-Lukas
[EMAIL PROTECTED] wrote:
Hi,
using Maven 1.1, I've read there was an option to use a proxy and also to
You can try to create an internal repository. This internal repository
will be your only one entry point (i.e.
maven.repo.remote=http://myintermalrepo.mycompany:8080)
And you will not have to use the proxy configuration.
Romain Gilles
Development Software Engineer
Reuters
(t) +33 (0)1 47 62
Try removing the http:
Yeah, I tried that - then Maven even complains that the protocol is missing
(plus it doesn't work either)
-
Only using a local repository isn't an option either - we are a big developer
team, distributed over various locations, and there will always be someone
You are right, the http is correct actually. Another guess: replace the
IP name by a DNS name? But you will have to tell us more details about
the problem, just saying it doesn't work doesn't leave me a lot of
clues...
Well, actually, using a DNS name is just what I really want and so what
You are right, the http is correct actually. Another guess: replace the
IP name by a DNS name? But you will have to tell us more details about
the problem, just saying it doesn't work doesn't leave me a lot of clues...
-Lukas
[EMAIL PROTECTED] wrote:
Try removing the http:
Yeah, I tried
Nope, we don't need a proxy username or password -
plus, the IP I wrote down is the IP that should NOT use a proxy.
When I type in the IP into my browser, I can see the maven repository.
And when I remove the proxy setting it also works in Maven.
With these settings:
Well, that must be a permission problem, check your server logs, maybe
just a wrong pwd (don't you need maven.proxy.password?), or wrong
directory permissions?
And yes, I can confirm that maven.proxy.nonProxyHosts is an existing
property [1] and that it is used by DependencyVerifier, even
