[
https://issues.jboss.org/browse/JBRULES-1466?page=com.atlassian.jira.plug...
]
Geoffrey De Smet resolved JBRULES-1466.
---------------------------------------
Resolution: Rejected
This is not a good idea: if we hard code the expected MVEL version inside drools
if (MVEL.VERSION != "2.0" && MVEL.VERSION_SUB = "17") {...}
then we create 2 problems:
- drools would crash if a higher, backward-compatible version of mvel is used, for example
because another dependency (ZK) needs a more up-to-date mvel version.
- maintenance problem to keep that version in sync
Furthermore, following the same logic, we'd have to check in drools-compiler if a
compatible drools-core version is used. And so on for all modules and all dependencies.
Instead, your build system should protect you from the "throw all jars in a lib
directory" mess.
Use a build system that understand transitive dependencies, such as maven, ant+ivy,
gradle, ...
please bail if user is using an incompatible MVEL
-------------------------------------------------
Key: JBRULES-1466
URL:
https://issues.jboss.org/browse/JBRULES-1466
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.0.4, 4.0.5
Reporter: Godmar Back
Assignee: Geoffrey De Smet
Fix For: 5.2.0.CR1
When using MVEL, please check String constants org.mvel.MVEL.VERSION and
org.mvel.MVEL.VERSION_SUB to see if it's compatible. Bail if it isn't.
Ignoring version mismatches leads to difficult to diagnose problems, see:
http://lists.jboss.org/pipermail/rules-users/2008-February/004759.html
http://lists.jboss.org/pipermail/rules-users/2008-February/004709.html
Thanks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira