-
Feature Request
-
Resolution: Done
-
Minor
-
None
-
None
- Customers really prefer to have a features.xml when using optaplanner in an OSGi environment
- QA's testing framework really prefers to have a features.xml, even to just test the already existing optaplanner-core manifest.mf metadata.
It will be put in drools-karaf-features (which should be really called kie-karaf-features because it holds jbpm and optaplanner features too).
- is related to
-
PLANNER-387 Add optional classloader parameter into SolverFactory methods, especially for OSGi
- Resolved