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

Mon Jun 6 08:08:59 EDT 2011

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

Kristof Vanbecelaere commented on JBBUILD-682:
----------------------------------------------

I think revoking access to the deprecated repository was a pretty radical move. If you currently generate an app using the weld archetype jboss-javaee6-webapp and build it starting from an empty m2 repository and with profile arq-jbossas-remote enabled you will find that it needs many of the dependencies listed in the left-side column in http://community.jboss.org/wiki/JBossDeprecatedRepository. Anyone coming to jboss via the archetype will have a poor development experience.

> 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