Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-12631

remove Flow, jbpm4, and jpdl stuff from SVN in trunk

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.0.0.Alpha1-SOA
    • 3.3.0.Final-SOA
    • jbpm
    • None

      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:

      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
      

      Is that correct?

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: