Description of problem: When customer uses a wizard to create a jBPM project, community version name,"6.0.0.Final", is used for a jbpm.version variable in jBPM project's pom.xml. Since JBDS and Integration Stack are official product, product version name should be used. Version-Release number of selected component (if applicable): JBoss Developer Studio 7.1.1.GA JBoss Developer Studio Integration Stack 7.0.2 Steps to Reproduce: 1. Start JBDS 2. New -> jBPM -> jBPM project(Maven) Actual results: Generated pom.xml === ~~ <properties> <jbpm.version>6.0.0.Final</jbpm.version> </properties> ~~ <dependencies> <dependency> <groupId>org.jbpm</groupId> <artifactId>jbpm-test</artifactId> <version>${jbpm.version}</version> </dependency> </dependencies> </project> === Expected results: On the wizard, user can select a product version for JBoss BPM Suite, and appropriate value will be set to the jbpm.version. Additional info: For JBoss BPM Suite 6.0.1, "6.0.2-redhat-6" should be used. For JBoss BPM Suite 6.0.2, "6.0.3-redhat-4" should be used.
Imho, I don't think this should be changed. The wizard simply creates a simple project that customers then customize according to their needs. It's trivial to change the pom.xml to whatever version of the product you want to use. Even if we try to change this, what version should we use? As there will always be multiple versions of the product in support. And would it mean we'll have to keep the versions in sync (do an update whenever a new version of the product is released)?
Will consider improvements in the future. For example, offering an explicit dialog where the user can specify the version that should be used. This wizard might even be able to make a suggestion to the user based on available runtimes.
Alessandro, would it be sufficient if we add an editable text field in the jBPM Maven wizard where the user can specify which version of jBPM he wants to use (by default this will be the latest community Final release, so 6.3.0.Final now)?
Yes Kris, a dialog window will work well, and a suggestion based in the configured runtime is still better. But see that we will need another change too. Currently the pom generated does not use our BOM. The project is supposed to set it given that the BOM usage is comething still not clear for our customers. Having it already set will help a lot.