[
https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi...
]
supun Malinga commented on JBBUILD-682:
---------------------------------------
Hi,
I'm also affected by the same issue. Accoeding to the discussion it seems the
workaround is to add parameters to .m2/settings.xml file. But its not practical to
instruct each user who is building a project to do this. Would appriciate if there is a
more easier fix.
thanks,
http://repository.jboss.org/maven2/ serving HTTP 403 to hosts outside
RedHat VPN
--------------------------------------------------------------------------------
Key: JBBUILD-682
URL:
https://issues.jboss.org/browse/JBBUILD-682
Project: JBoss Build System
Issue Type: Bug
Reporter: Marek Schmidt
Assignee: Paul Gier
Priority: Critical
Fix For: Build Support 2012
The legacy maven repository
http://repository.jboss.org/maven2/ is serving HTTP 403 to
hosts outside RedHat VPN, causing lots of builds to fail.
e.g.
http://community.jboss.org/message/606819?tstart=0 with error:
Access denied to:
http://repository.jboss.org/maven2/trove/trove/2.1.1/trove-2.1.1.pom
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira