[
https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi...
]
Marek Schmidt commented on JBBUILD-682:
---------------------------------------
My problem was that this repository was configured in some dependency of some outdated
version of some jboss artifact. (probably it was
org.jboss.jbossas:jboss-as-client:6.0.0.20100911-M5 or some of its dependency). It looks
like quite a lot of poms from the nexus repository declare the
http://repository.jboss.org/maven2/ repository
The build fails for anybody outside of redhat, but works for me, which made it difficult
to diagnose the problem.
Furthermore, I have noticed a page
http://community.jboss.org/wiki/MavenSettings
Where you state
{quote}
As of April 2010, the JBoss Community no longer uses the old repository URL.
http://repository.jboss.org/maven2/
This URL will remain available indefinitely for compatibility with old builds.
{quote}
;)
Now, it is a good thing that it didn't work, as it made me realize the outdated
dependency, but if that is the purpose of the repository not working, maybe it should be
configured exactly the opposite way: not working for people in redhat, and available for
people outside, for compatibility reasons :)
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