[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4319) Include jbpm4 into build

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-4319:
-----------------------------------

Build is happy. 2 test suites are running. Please refresh your workspace with my changes in svn (including changes to the tests feature and releng project), and try again.

Then, verify the contents of the Update zip are valid and can be installed into a clean Eclipse JEE bundle. http://www.eclipse.org/downloads/?tab=developer

After that I'll figure out how to hook the output of this build into the JBT build (rather than just rebuilding it using the old way).

> Include jbpm4 into build
> ------------------------
>
>                 Key: JBIDE-4319
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4319
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: Build/Releng, jbpm
>            Reporter: Max Rydahl Andersen
>            Assignee: Koen Aers
>             Fix For: 3.1.0.M2
>
>         Attachments: build0.txt
>
>
> We should get jbpm4 into the jbosstools build so it becomes accessible and available for testing.
> As discussed on phone we will initially just want this in the JBT build, but not in JBDS and we are ok with having jbpm3 and jpbm4 overlap with functionallity for a while as long as when we reach GA the two will be aligned/compatible.
> Koen, first step is for you to add info here on which svn/cvs plugins/features we need to include and then reassign this to Nick who can help out integrate it into our current build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira