[jbosstools-issues] [JBoss JIRA] (JBIDE-15341) use latest parent pom & target platform so we can release BPEL tooling v 1.2.100.Final

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-15341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBIDE-15341:
-------------------------------

    Description: 
Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha1-SNAPSHOT.

Target platform referenced should be the Kepler version (4.1.x) rather than the Juno version (4.0.0).

Once that's fixed and the build is blue, we should release bpel tooling v 1.2.100.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds.

  was:
Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha2-SNAPSHOT.

Target platform referenced should be the Kepler version (4.1.x) rather than the Juno version (4.0.0).

Once that's fixed and the build is blue, we should release jbpm3 tooling v 4.5.200.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds.


    
> use latest parent pom & target platform so we can release BPEL tooling v 1.2.100.Final
> --------------------------------------------------------------------------------------
>
>                 Key: JBIDE-15341
>                 URL: https://issues.jboss.org/browse/JBIDE-15341
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: BPEL
>    Affects Versions: 4.1.0.Final
>            Reporter: Nick Boldt
>            Assignee: Koen Aers
>             Fix For: 4.1.0.Final
>
>
> Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha1-SNAPSHOT.
> Target platform referenced should be the Kepler version (4.1.x) rather than the Juno version (4.0.0).
> Once that's fixed and the build is blue, we should release bpel tooling v 1.2.100.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira