[
https://issues.jboss.org/browse/JBIDE-12631?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-12631:
-------------------------------
Summary: remove Flow, jbpm4, and jpdl stuff from SVN in trunk (was: merge Flow
component into jBPM3 component in SVN? Or remove it entirely?)
remove Flow, jbpm4, and jpdl stuff from SVN in trunk
----------------------------------------------------
Key: JBIDE-12631
URL:
https://issues.jboss.org/browse/JBIDE-12631
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.3.0.Final-SOA
Reporter: Nick Boldt
Assignee: Koen Aers
Fix For: 4.0.0.Alpha1-SOA
Koen:
Is there any reason to keep the Flow component separated from the jbpm3/4 component in
SVN?
If we merge them we can build them in ONE step instead of TWO, saving time and
resources.
Actually, is Flow even still needed? Or was that a sidetrack for jbpm4 only, and thus can
be deprecated/removed?
My feeling is that we can purge everything in Flow and all the jbpm4 stuff from SVN,
leaving only these IUs:
{code}
org.jbpm.gd.jpdl.feature
org.jboss.tools.jbpm3.feature
org.jboss.tools.jbpm3.test.feature
org.jboss.tools.jbpm.convert.feature
org.jboss.tools.jbpm.common.feature
org.jboss.tools.jbpm.common
org.jboss.tools.jbpm.convert
org.jbpm.gd.jpdl
org.jboss.tools.jbpm.common.test
org.jboss.tools.jbpm.convert.test
org.jbpm.gd.jpdl.test
org.jboss.tools.jbpm.ui.bot.test
{code}
Is that correct?
--
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