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

Split SOA components out of JBoss Tools aggregate site; create 2nd aggregate for SOA Tooling

    XMLWordPrintable

Details

    Description

      The following components should be aggregated in a NEW aggregate build and removed from the existing one:

      Drools 5.2
      Flow/jBPM
      BPMN2 (there is no JIRA component for this yet)
      BPEL (moving to Eclipse.org)
      Teiid
      Modeshape
      ESB
      Smooks

      1. Fix ~/trunk/build/aggregate/ - remove components from site.xml

      2. Create new ~/trunk/build/aggregate-soa/ - add components to site.xml

      3. Create new aggregate jobs:

      4. get new www.jboss.org/soatools/ site, publish there instead of www.jboss.org/tools/, and cross link project pages. Was this idea nixed? Don't see documented evidence, just vague recollection.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users JBDS-1779 JBDS50_0435: [COMMIT] (Dev) Externalize SOA-P Features

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1831 Missing Teiid dependencies while installing from SOA-P tooling site

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is blocked by

          Sub-task - The sub-task of the issue JBIDE-9219 Split up continuous and test builds for SOA/JBDS split

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Feature Request - Feature requests from customers and/or users JBIDE-8734 Update Site containing JBT Bot Tests

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1823 Remove Smooks Editor from JBDS

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-9565 compile failed in org.jboss.tools.deltacloud.ui.bot.test :: The import org.jboss.tools.ui.bot.ext.config.Annotations.SWTBotTestRequires cannot be resolved

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. JBDS-1688 remove refs to jbpm from jbds product (intro content, themes, wizards, etc.)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. JBDS-1689 remove refs to esb from jbds product (intro content, themes, wizards, etc.)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. JBDS-1691 remove refs to soa from jbds product (intro content, themes, wizards, etc.)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-engineering-dpalmer Douglas Palmer
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: