[
https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi...
]
Paul Gier commented on JBBUILD-682:
-----------------------------------
Yes, I see your point. I would like to enforce that the repo not be used by jboss
employees. The idea of keeping it available for internal employees was to prevent
breaking old product builds. But maybe we can just password protect it for internal
builds.
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 2011
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.
For more information on JIRA, see:
http://www.atlassian.com/software/jira