[jboss-jira] [JBoss JIRA] (JBBUILD-682) http://repository.jboss.org/maven2/ serving HTTP 403 to hosts outside RedHat VPN
Larry O'Leary (JIRA)
jira-events at lists.jboss.org
Fri Apr 20 16:31:18 EDT 2012
[ https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12686211#comment-12686211 ]
Larry O'Leary commented on JBBUILD-682:
---------------------------------------
This issue also occurs when attempting to build JBoss ON 2.4.2 which was just released a few weeks ago. It was a maintenance release so obviously it has dependencies on legacy packages. For example, it requires jboss-packaging-maven-plugin-1.9.99.jar. However, the build fails because the artifact can not be downloaded due to the Forbidden error message received by Maven.
I looked into using a version from Nexus however this version does not exist there.
I am connected to the VPN but the build still failed. It was pointed out that the internal IP address of repository.jboss.org is 10.5.105.13 while the external is 209.132.182.33. In my case, I use my local DNS server for all things except for specific internal domains. repository.jboss.org was not one of them. I changed my DNS configuration to direct DNS lookups for repository.jboss.org to the RH internal DNS server and I am back up and running. Obviously this solution only works for building when connected to the RH VPN. Community users who attempt to build the upstream will continue to fail if they attempt to build these previous releases.
> 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
More information about the jboss-jira
mailing list