Use Maven for compiling the workbench projects ---------------------------------------------- Key: DROOLS-1398 URL: https://issues.jboss.org/browse/DROOLS-1398 Project: Drools Issue Type: Feature Request Reporter: Toni Rikkola Assignee: Mario Fusco We currently use the kie-maven-plugin internally to compile the kjar's and only use Maven to provide the information about parent projects and dependencies for the project. Yet we have the power of Maven underneath and we do not use it. It is impossible to use simple features like ignoring folders or moving code. Or more complicated, for example if you have your own rule asset format and need a Maven plugin to generate the DRL out of it. However it is possible to set this functionality up. This causes problems: * Same git tag built in the workbench produce different results depending on the Workbench version that is being used. This means that if you want to rebuild a lost kjar, you need to install the same workbench version that was originally used to create the first one * Projects build in command line/build server can produce different kjars than the ones built with the workbench Benefits we gain for going full Maven: * Build the same artifacts anywhere * Make Maven build cycle usable * Make Maven plugins usable * Run tests with any test tooling, users are not limited to Test Scenarios What to keep in mind: * If we let the user set the KIE version for the kie-maven-plugin. The internal compiler still uses the version the workbench has.