Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-283

By JBDS community version name is used for a jbpm.version variable in jBPM project's pom.xml

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Critical Critical
    • None
    • 6.0.2
    • Eclipse Tooling
    • None

      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.

            mnovotny@redhat.com Marek Novotny
            rhn-support-hfuruich Hisao Furuichi
            Jozef Marko Jozef Marko (Inactive)
            Jozef Marko Jozef Marko (Inactive)
            Alessandro Lazarotti, Kris Verlaenen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: