[
https://issues.jboss.org/browse/JBIDE-12631?page=com.atlassian.jira.plugi...
]
Koen Aers commented on JBIDE-12631:
-----------------------------------
Okay, so I took a look at it to refresh my memory and this is the situation:
org.jboss.tools.jpdl4 depends on org.jboss.tools.flow.common and on
org.jboss.tools.jbpm.common
org.jbpm.gd.jpdl depends on org.jboss.tools.jbpm.common
For JBDS (for which jpdl4 is not included) org.jboss.tools.flow.common is not needed.
For JBT the situation depends: if jpdl4 support can be dropped then
org.jboss.tools.flow.common is not needed in the other case it is.
So if jpdl4 support can be dropped (not sure who has to decide that),
org.jboss.tools.flow.common can be purged. In the other case org.jboss.tools.flow.common
can be merged with org.jboss.tools.jpdl4.
merge Flow component into jBPM3 component in SVN? Or remove it
entirely?
------------------------------------------------------------------------
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