1:16 p.m.
Nick Boldt created JBIDE-12631:
----------------------------------
Summary: merge Flow component into jBPM3 component in SVN?
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
1:16 p.m.
New subject: [JBoss JIRA] (JBIDE-12631) merge Flow component into jBPM3 component in SVN? Or remove it entirely?
[
https://issues.jboss.org/browse/JBIDE-12631?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-12631:
-------------------------------
Summary: merge Flow component into jBPM3 component in SVN? Or remove it entirely?
(was: merge Flow component into jBPM3 component in SVN?)
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
1:10 a.m.
New subject: [JBoss JIRA] (JBIDE-12631) merge Flow component into jBPM3 component in SVN? Or remove it entirely?
[
https://issues.jboss.org/browse/JBIDE-12631?page=com.atlassian.jira.plugi...
]
Koen Aers commented on JBIDE-12631:
-----------------------------------
Nick,
I don't know the actual status of this but 'flow' was created to catch all the
commonalities between the jpdl 4, seam flow and rule flow editors. I'm pretty sure
that rule flow has never used it but jpdl 4 and seam flow were both using it.
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
2:28 a.m.
New subject: [JBoss JIRA] (JBIDE-12631) merge Flow component into jBPM3 component in SVN? Or remove it entirely?
[
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
11:27 a.m.
New subject: [JBoss JIRA] (JBIDE-12631) merge Flow component into jBPM3 component in SVN? Or remove it entirely?
[
https://issues.jboss.org/browse/JBIDE-12631?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12631:
------------------------------------
In terms of the TOOLING, we build Seam tools w/o jbpm4 or flow being present. This is
especially true now that jbpm/flow are "SOA Tooling" components which are built
downstream from the "Core" components, of which Seam is one.
I can't speak to the RUNTIMES, however -- I just know the dependency order for
building the various tooling components.
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
1:41 p.m.
New subject: [JBoss JIRA] (JBIDE-12631) merge Flow component into jBPM3 component in SVN? Or remove it entirely?
[
https://issues.jboss.org/browse/JBIDE-12631?page=com.atlassian.jira.plugi...
]
Koen Aers commented on JBIDE-12631:
-----------------------------------
The seam pageflow editor is actually in the jbpm 3 plugin (org.jbpm.gd.jpdl) and afaik
nowhere else. But then I don't know if seam pageflow is still used at all. I guess not
since org.jbpm.gd.jpdl is only in SOA tooling for quite some time now and we didn't
have any complaints about it ;-)
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
10:24 a.m.
New subject: [JBoss JIRA] (JBIDE-12631) merge Flow component into jBPM3 component in SVN? Or remove it entirely?
[
https://issues.jboss.org/browse/JBIDE-12631?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12631:
------------------------------------
So I'm planning to delete everything in the jbpm folder in SVN from trunk except the
features/plugins listed above.
Last chance to tell me that's a bad idea. Going once... going twice...
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
10:26 a.m.
New subject: [JBoss JIRA] (JBIDE-12631) merge Flow component into jBPM3 component in SVN? Or remove it entirely?
[
https://issues.jboss.org/browse/JBIDE-12631?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12631 at 9/19/12 11:25 AM:
--------------------------------------------------------------
Based on offline discussions w/ [~burrsutter], [~manaRH], and [~koen.aers], no one has any
objections to the stated plan above -- to delete everything in the jbpm folder in SVN from
trunk but for the features/plugins listed above.
Last chance to tell me that's a bad idea. Going once... going twice...
was (Author: nickboldt):
So I'm planning to delete everything in the jbpm folder in SVN from trunk except
the features/plugins listed above.
Last chance to tell me that's a bad idea. Going once... going twice...
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
10:32 a.m.
New subject: [JBoss JIRA] (JBIDE-12631) merge Flow component into jBPM3 component in SVN? Or remove it entirely?
[
https://issues.jboss.org/browse/JBIDE-12631?page=com.atlassian.jira.plugi...
]
Koen Aers commented on JBIDE-12631:
-----------------------------------
+1 for removing from me
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
10:55 a.m.
New subject: [JBoss JIRA] (JBIDE-12631) remove Flow, jbpm4, and jpdl stuff from SVN in trunk
[
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
12:25 p.m.
New subject: [JBoss JIRA] (JBIDE-12631) remove Flow, jbpm4, and jpdl stuff from SVN in trunk
[
https://issues.jboss.org/browse/JBIDE-12631?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12631:
------------------------------------
Flow, jbpm4m and jpdl have been removed from trunk.
{code}
------------------------------------------------------------------------
r43837 | nickboldt | 2012-09-19 13:23:38 -0400 (Wed, 19 Sep 2012) | 2 lines
Changed paths:
M download.jboss.org/jbosstools/builds/cascade/swimlanes.txt
JBIDE-12631 remove flow, jbpm4, jpdl4 from svn trunk - available from 4.0.0.Alpha1 branch
or 3.3.x branch
------------------------------------------------------------------------
r43836 | nickboldt | 2012-09-19 13:18:00 -0400 (Wed, 19 Sep 2012) | 2 lines
Changed paths:
M jbpm/features/org.jboss.tools.jbpm.common.feature/feature.xml
M jbpm/features/org.jboss.tools.jbpm.common.feature/pom.xml
...
M jbpm/plugins/org.jbpm.gd.jpdl/META-INF/MANIFEST.MF
M jbpm/plugins/org.jbpm.gd.jpdl/pom.xml
M jbpm/plugins/pom.xml
M jbpm/pom.xml
M jbpm/site/pom.xml
...
M jbpm/tests/org.jbpm.gd.jpdl.test/META-INF/MANIFEST.MF
M jbpm/tests/org.jbpm.gd.jpdl.test/pom.xml
M jbpm/tests/pom.xml
JBIDE-12631 bump all jbpm plugins to 4.5.0 (largest version + 0.1.0)
------------------------------------------------------------------------
r43834 | nickboldt | 2012-09-19 12:05:59 -0400 (Wed, 19 Sep 2012) | 2 lines
Changed paths:
M build/pom-soa-tooling.xml
JBIDE-12631 remove flow, jbpm4, jpdl4 from svn trunk - available from 4.0.0.Alpha1 branch
or 3.3.x branch
------------------------------------------------------------------------
r43833 | nickboldt | 2012-09-19 12:03:58 -0400 (Wed, 19 Sep 2012) | 2 lines
Changed paths:
D jbpm/features/org.jboss.tools.flow.jpdl4.feature/.project
...
JBIDE-12631 remove flow, jbpm4, jpdl4 from svn trunk - available from 4.0.0.Alpha1 branch
or 3.3.x branch
------------------------------------------------------------------------
{code}
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
12:49 p.m.
New subject: [JBoss JIRA] (JBIDE-12631) remove Flow, jbpm4, and jpdl stuff from SVN in trunk
[
https://issues.jboss.org/browse/JBIDE-12631?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-12631.
------------------------------
Assignee: Nick Boldt (was: Koen Aers)
Resolution: Done
Closing. Built fine in trunk locally (though the 4.0_trunk job is disabled in Jenkins for
now).
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: Nick Boldt
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
4955
days inactive
4957
days old
jbosstools-issues@lists.jboss.org
11 comments
2 participants
participants (2)
-
Koen Aers (JIRA) -
Nick Boldt (JIRA)