Bug 1126733 - Generate KJAR Project
Summary: Generate KJAR Project
Keywords:
Status: ASSIGNED
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Eclipse Tooling
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Kris Verlaenen
QA Contact: Jozef Marko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-05 07:29 UTC by Anton Giertli
Modified: 2018-01-30 12:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Feature Request


Attachments (Terms of Use)

Description Anton Giertli 2014-08-05 07:29:17 UTC
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


Note You need to log in before you can comment on or make changes to this bug.