[jbosstools-issues] [JBoss JIRA] (JBIDE-12631) remove Flow, jbpm4, and jpdl stuff from SVN in trunk

[Nick Boldt (JIRA)]

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

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