[ https://issues.redhat.com/browse/DROOLS-6020?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-6020: --------------------------------- Description: Currently in the executable model the `drools-model-compiler` has the code to generate executable model DSL under the package `org.drools.modelcompiler.builder.generator` and the interpreter that takes the DSL as the input and outputs the RETE under the `org.drools.modelcompiler` package. These two packages can be split in two modules, i.e. drools-executable-model-compiler drools-executable-model-runtime So that when having a KJAR with the DSL compiled, only the latter is needed to execute it. Note that currently the compiler outputs the DSL based on these classes {code:java} package org.drools.modelcompiler.dsl.flow; public class D extends FlowDSL { } public class D extends PatternDSL { } {code} And this has to be changed, as while executing it there'll be no modelcompiler jar. At the same time we should keep a copy of those classes in that position so that we don't loose backwards compilation was: Currently in the executable model the `drools-model-compiler` has the code to generate executable model DSL under the package `org.drools.modelcompiler.builder.generator` and the interpreter that takes the DSL as the input and outputs the RETE under the `org.drools.modelcompiler` package. These two packages can be split in two modules, i.e. drools-executable-model-compiler drools-executable-model-runtime So that when having a KJAR with the DSL compiled, only the latter is needed to execute it. Note that currently the compiler outputs the DSL based on these classes {code:java} package org.drools.modelcompiler.dsl.flow; public class D extends FlowDSL { } public class D extends PatternDSL { } {code} And this has to be changed, as while executing it there'll be no modelcompiler jar. -- This message was sent by Atlassian Jira (v8.13.1#813001)