[
https://jira.jboss.org/browse/JBPM-2838?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar updated JBPM-2838:
-----------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Moved jboss-j2ee dependency of jbpm-api pom to scope 'provided'
Added jboss-j2ee dependency to integration-console and test-base to compensate
Mark jboss-j2ee dependency as scope=provided
--------------------------------------------
Key: JBPM-2838
URL:
https://jira.jboss.org/browse/JBPM-2838
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Reporter: M M
Assignee: Alejandro Guizar
Fix For: jBPM 4.4
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Please mark the dependency on jboss as <scope>provided</scope>
Here is the relevent section of the jbpm-api pom:
<dependencies>
<dependency>
<groupId>jboss</groupId>
<artifactId>jboss-j2ee</artifactId>
</dependency>
</dependencies>
This is not an issue of determining minimal dependency (it certainly needs this
dependency), but rather, decoupling the jbpm api from any specific J2EE vendor
implementation or version. Users of the jbpm api will then not have a transitive
dependency on a specific version of jboss.
The current workaround is to exclude this dependency when depending on the jbpm api.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira