I'm sorry to hear that, but I hope you see that if we remove
<repository> declaration from the POM, that will break other people's
builds as Maven no longer can find artifacts for them.
It seems to me that the real culprit is your HTTP proxy. If the proxy
has a policy of prohibiting access to java.net repositories. they should
report appropriate HTTP status code to indicate that, like 401, instead
of just letting it hang.
I believe another work around is for you to touch up our POM a bit when
you add that to your Nexus.
Jackson, Brian R wrote:
> We have an internal Nexus repository and all our Maven traffic must go
> through it but recently I added org.jvnet.staxex:stax-ex as a dependency to
> my project and now my builds try to check the java.net repositories directly
> and hang because of our internal HTTP proxy.
>
> Išve solved it by having Maven treat our internal repository as a mirror of
> java.net, java.net2 and java.net1. But it would be nice if you released a
> new version with the repository declarations stripped out of the pom.xml.
>
> Thanks,
> ___________________________________________
> Brian R. Jackson
> Staff Software Engineer
> ESPN.com Fantasy Games
> (860) 766-2511
>
>
>
--
Kohsuke Kawaguchi
Sun Microsystems http://weblogs.java.net/blog/kohsuke/