[
https://jira.jboss.org/browse/JBPM-2503?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar resolved JBPM-2503.
------------------------------------
Labels: dependency jbpm3 maven (was: )
Assignee: Alejandro Guizar
Resolution: Done
I conducted an in-depth review of the jbpm-jpdl dependencies prior to releasing 3.2.10,
unaware of this issue report. In particular, jackrabbit-core was marked as optional as
requested here.
Maven pom file for jbpm-jpdl should define jackrabbit-core dependency
as optional
---------------------------------------------------------------------------------
Key: JBPM-2503
URL:
https://jira.jboss.org/browse/JBPM-2503
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 3.2.6.SP1, jBPM 3.2.5.SP5
Reporter: Marek Novotny
Assignee: Alejandro Guizar
Priority: Minor
Labels: jbpm3, maven, dependency
jackrabbit-core implementation of JCR should be defined as optional dependency, because
any maven based project which doesn't need to use JCR jbpm feature downloads this
dependency and also its transitive dependencies.
If you look at
http://maven.apache.org/guides/introduction/introduction-to-optional-and-...,
there is clear description why use <optional>true</optional> in maven
project.
Please fix the jbpm-jpdl pom file.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira