[
https://jira.jboss.org/jira/browse/JBIDE-4319?page=com.atlassian.jira.plu...
]
Nick Boldt commented on JBIDE-4319:
-----------------------------------
Things I need:
* a jBPM "all-in-one" or SDK feature (to include runtime(s) + sources + examples
+ whatever else needs to be compiled and delivered; used for compiling and packaging)
* a jBPM "all tests" feature (to include all test plugins; used for compiling
and packaging)
For examples of these, see:
http://dev.eclipse.org/svnroot/technology/org.eclipse.linuxtools/releng/t...
http://dev.eclipse.org/svnroot/technology/org.eclipse.linuxtools/releng/t...
* a map file pointing at all your features, plugins, and fragments in SVN (or CVS, or
both)
http://dev.eclipse.org/svnroot/technology/org.eclipse.linuxtools/releng/t...
* updated MANIFEST.MF files to set correct version requirements/ranges (if needed) between
your plugins and dependencies
* a list of Eclipse and JBoss binary requirements needed to compile your sources &
tests and run them.
After that, we can work together on creating the rest of the code needed in your .releng
project:
http://dev.eclipse.org/svnroot/technology/org.eclipse.linuxtools/releng/t...
http://anonsvn.jboss.org/repos/jbosstools/trunk/jmx/releng/
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.M1, 3.1.0.M2
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