[
https://issues.jboss.org/browse/JBEE-112?page=com.atlassian.jira.plugin.s...
]
Paul Gier commented on JBEE-112:
--------------------------------
We can't push this one to central because we don't own the groupId. I guess we
could switch the build to use the upstream version of the artifact, the reason we
didn't before was to have the same dependency as AS7. I guess our javaee apis are
probably fine without the patches we included in the .jbossorg-2 version.
jboss-javaee-web Leaking Dependency to Nexus
--------------------------------------------
Key: JBEE-112
URL:
https://issues.jboss.org/browse/JBEE-112
Project: JBoss JavaEE Spec APIs
Issue Type: Bug
Reporter: Andrew Rubinger
Assignee: Paul Gier
org.jboss.spec:jboss-javaee-web-6.0 (which is propagated to Maven Central) is leaking a
dependency to xalan:xalan:2.7.1.jbossorg-2, which is not present in Maven Central.
{code}[DEBUG] org.ocpsoft.rewrite:rewrite-parent:pom:1.0.6-SNAPSHOT
[DEBUG] org.jboss.spec:jboss-javaee-web-6.0:pom:3.0.1.Final:test
[DEBUG] xalan:xalan:jar:2.7.1.jbossorg-2:test{code}
Either fix to the correct dependency (something in Central) or push the dependent
artifact to Central as well.
--
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