-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
None
-
2020 Week 40-42 (from Sep 28)
-
Undefined
-
NEW
-
NEW
-
---
-
---
Drools users have among their dependencies module like drools-core and drools-compiler that in reality are no more than "implementation details". This causes backward incompatibilities when we decide to split engine in finer grained submodules and descope optional features.
For this reason we decided to introduce 2 wrapper modules (for the 2 different main usage scenarios that I see at the moment), made by just a pom aggregating a list of dependencies. The suggested names for these modules are at the moment
- drools-engine aggregating drools-core, drools-compiler and drools-model-compiler
- drools-engine-classic aggregating drools-core, drools-compiler, drools-mvel (and eventually drools-serialization-protobuf)
Add comments to this ticket to suggest different names.
- is incorporated by
-
KOGITO-2851 Rule engine modularization
- Resolved