[
https://issues.jboss.org/browse/JBEE-150?page=com.atlassian.jira.plugin.s...
]
Shelly McGowan commented on JBEE-150:
-------------------------------------
[~trepel] Does it help your situation if include the Java EE API BOM for full or web
profile as the artifcat to your maven project instead of just jboss-jstl-api_1.2_spec.
Full Profile APIs:
https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j...
or Web Profile APIs only:
https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j...
I thought I had resolve that problem with exclusions using the BOMS (see also: JBEE-97,
JBEE-112, JBEE-118)
The jboss-jstl-api_1.2_spec artifact depends on xalan artifact that
is not present in Maven Central
---------------------------------------------------------------------------------------------------
Key: JBEE-150
URL:
https://issues.jboss.org/browse/JBEE-150
Project: JBoss JavaEE Spec APIs
Issue Type: Bug
Reporter: Tomas Repel
Assignee: Shelly McGowan
The org.jboss.spec.javax.servlet.jstl:jboss-jstl-api_1.2_spec:1.1.0.Final depends on
xalan:xalan:2.7.1.jbossorg-2 artifact, this one is not present in Maven Central.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira