Description of problem: Currently when the new jBPM project is generated via Eclipse it is not a kjar. It is not always desired to create KJAR, i.e. workitemhandlers, etc. But when user want to create his business assets using Eclipse the project should be packaged as a kjar. Add possibility to the tooling for generating a KJAR project. My personal idea was to include a checkbox after user selected jBPM (maven). ☑ Generate as KJAR There should also be description of what KJAR means and the list of the resources customer wants to add. BPMN ✔ DRL ✔ decision tables ✔ Each selected resource would be reflected in the final pom.xml in the plugin configuration, like this: <plugin> <groupId>org.kie</groupId> <artifactId>kie-maven-plugin</artifactId> <version>${drools.version}</version> <extensions>true</extensions> <dependencies> <dependency> <groupId>org.drools</groupId> <artifactId>drools-decisiontables</artifactId> <version>${drools.version}</version> </dependency> <dependency> <groupId>org.jbpm</groupId> <artifactId>jbpm-bpmn2</artifactId> <version>${drools.version}</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-simple</artifactId> <version>1.7.7</version> </dependency> </dependencies> </plugin> Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Create new jBPM project from Eclipse 2. It's not configured as a kjar Actual results: New jBPM project is not configured as a KJAr Expected results: There should be possibility to configure new jBPM project as a KJAR