[
https://issues.jboss.org/browse/JBBUILD-682?page=com.atlassian.jira.plugi...
]
Kristof Vanbecelaere edited comment on JBBUILD-682 at 6/6/11 9:38 AM:
----------------------------------------------------------------------
Mind you, it is not the archetypes that pose the problem. It is one of the transitive
dependencies of the generated app. The problem is, I cannot even run "mvn
dependency:tree" as long as I don't have all the dependencies in my repository.
So it is already hard to diagnose as it is. Try navigating the jboss pom forest using find
and grep.
was (Author: kva):
Mind you, it is not the archetypes that pose the problem. It is one of their
dependencies. The problem is, I cannot even run "mvn dependency:tree" as long as
I don't have all the dependencies in my repository. So it is already hard to diagnose
as it is. Try navigating the jboss pom forest using find and grep.
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