]
Geoffrey De Smet edited comment on WELD-956 at 8/29/11 10:32 AM:
-----------------------------------------------------------------
@Marek I agree that WELD-952 is the real bug,
but not allowing outsiders to build meanwhile is a bit harsh :)
was (Author: ge0ffrey):
@Marek I agree that WELD-952 is the real bug,
but not allowing outsiders the build meanwhile is a bit harsh :)
Outside the VPN it's impossible to build weld from source with an
empty maven repository because
repository.jboss.org/maven2 is forbidden
-----------------------------------------------------------------------------------------------------------------------------------------
Key: WELD-956
URL:
https://issues.jboss.org/browse/WELD-956
Project: Weld
Issue Type: Task
Reporter: Geoffrey De Smet
Priority: Optional
To reproduce:
- Disconnect from the VPN
- rm -Rf ~/.m2/repository/apache-log4j/
- clone
https://github.com/weld/core as weld-core
- cd weld-core
- mvn clean install -DskipTests
result:
{code}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 20.507s
[INFO] Finished at: Mon Aug 29 14:02:33 CEST 2011
[INFO] Final Memory: 27M/492M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project weld-core-test: Could not resolve dependencies
for project org.jboss.weld:weld-core-test:jar:1.1.3-SNAPSHOT: Failed to collect
dependencies for [org.testng:testng:jar:jdk15:5.10 (compile),
org.jboss.test-harness:jboss-test-harness:jar:1.1.0-CR9 (compile),
org.jboss.test-harness:jboss-test-harness-jboss-as-60:jar:1.1.0-CR9 (test),
javax.el:el-api:jar:2.2 (compile), org.glassfish.web:el-impl:jar:2.1.2-b04 (compile),
org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec:jar:1.0.0.Beta2 (compile),
org.jboss.weld:weld-core:jar:1.1.3-SNAPSHOT (compile),
org.jboss.weld:weld-spi:jar:1.1.Beta2 (compile), org.jboss.weld:weld-api:jar:1.1.Beta2
(compile),
org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:jar:1.0.0.Beta1
(compile), org.jboss.interceptor:jboss-interceptor-spi:jar:2.0.0.CR1 (compile),
org.jboss.interceptor:jboss-interceptor-core:jar:2.0.0.CR1 (compile),
org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:jar:1.0.0.CR2 (compile),
org.slf4j:slf4j-simple:jar:1.5.10 (test), javax.transaction:jta:jar:1.1 (compile),
javax.persistence:persistence-api:jar:1.0 (compile),
javax.validation:validation-api:jar:1.0.0.GA (compile), javax.faces:jsf-api:jar:2.0.2-FCS
(compile), net.sourceforge.htmlunit:htmlunit:jar:2.4 (compile),
org.jboss.weld.arquillian.container:arquillian-weld-ee-embedded-1.1:jar:1.1.3-SNAPSHOT
(provided)]: Failed to read artifact descriptor for apache-log4j:log4j:jar:1.2.14: Could
not transfer artifact apache-log4j:log4j:pom:1.2.14 from/to
repository.jboss.org
(
http://repository.jboss.org/maven2/): Access denied to:
http://repository.jboss.org/maven2/apache-log4j/log4j/1.2.14/log4j-1.2.14... -> [Help
1]
{code}
Why? Inside the VPN you can connect to
http://repository.jboss.org/maven2/apache-log4j/log4j/1.2.14/log4j-1.2.14...
But outside the VPN you get "FORBIDDEN" instead for that url.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: