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

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796953#comment-12796953 ] 

Nick Boldt commented on JBIDE-15338:
------------------------------------

Kicked jBPM3 and it's blue, ready for aggregation:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk.component--jbpm/2005/

http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.0_trunk.component--jbpm/all/repo/

Should we copy this into a safer / stabler location, like Paul did for ESB [1] ? Perhaps this location [2] would make sense?

[1] http://download.jboss.org/jbosstools/updates/development/kepler/integration-stack/esb/1.5.0.Final/

[2] http://download.jboss.org/jbosstools/updates/stable/kepler/integration-stack/jbpm/4.5.200.Final/

                
> use latest parent pom & target platform so we can release jBPM3 tooling v 4.5.200.Final
> ---------------------------------------------------------------------------------------
>
>                 Key: JBIDE-15338
>                 URL: https://issues.jboss.org/browse/JBIDE-15338
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jbpm
>    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.Alpha2-SNAPSHOT.
> Target platform referenced should be the Kepler version (4.1.1.Final) 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.

--
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