[
https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi...
]
Savas Ali Tokmen edited comment on JBBUILD-682 at 7/2/11 11:21 AM:
-------------------------------------------------------------------
Hello
Even if JBoss does not want to reenable the repository, can JBoss please at least comply
with usual standards and return an error 404 instead of an error 403?
Maven actually thinks that something is wrong with the project when there is an error 403.
Returning an error 404 will at least help builds not fail.
Thank you
was (Author: alitokmen):
Hello
Even if JBoss does not want to reenable the repository, can JBoss please at least comply
with usual standards and return an error 404 instead of an error 401?
Thank you
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