[
https://jira.jboss.org/browse/JBPM-2957?page=com.atlassian.jira.plugin.sy...
]
Kris Verlaenen commented on JBPM-2957:
--------------------------------------
The jBPM5 modules are not dependent on the Drools rule components, but on the generic
implementation for setting up sessions, handling expression dialects, XML parsing, etc.
The jBPM5 engine can run without a rule engine being instantiated. Unfortunately, this
generic functionallity inside the Drools project is not modularized into a separate
module, so the jBPM5 module needs to depend on the drools-core module for this. If the
Drools project is refactored to separate out the generic functionality, the dependencies
could be updated.
Note that jBPM5 does depend on the rule engine for some more advanced node types as
defined in the BPMN2 specification, like rule tasks, conditional events, rule constraints
as expression language, etc. In that case, we do need to depend on the actual Drools rule
engine implementation.
I'm not sure this is something we can solve short term, but since the only impact is
that there might be some unused classes on your classpath, I think it's only a minor
issue.
Drools dependencies from the main pom.xml
-----------------------------------------
Key: JBPM-2957
URL:
https://jira.jboss.org/browse/JBPM-2957
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 5.0 Alpha
Environment: jBPM 5.0 alpha
Reporter: eric schabell
Assignee: Kris Verlaenen
Priority: Minor
Fix For: jBPM 5.x
The main pom.xml can be cleaned up to either remove or modularize the Drools deps
out/into separate module so that it is an optional component for user that want to use
jBPM5 without rules components.
--
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