[jboss-jira] [JBoss JIRA] (JBBUILD-682) http://repository.jboss.org/maven2/ serving HTTP 403 to hosts outside RedHat VPN

[Trenton Taylor (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646852#comment-12646852 ] 

Trenton Taylor commented on JBBUILD-682:
----------------------------------------

As a new user to Maven, I found this work-around to this issue. Add the following to your .m2/settings.xml:

<mirrors>
	<mirror>
		<id>jboss2-mirror</id>
		<mirrorOf>jboss.maven</mirrorOf>
		<url>http://repository.jboss.org/nexus/content/repositories/deprecated</url>
	</mirror>
</mirrors>

This will over-ride the use of the 'jboss.maven' default URL. It may not be the best solution, but it works.
                
> 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.
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