Uploaded image for project: 'Red Hat CodeReady Studio (devstudio)'
  1. Red Hat CodeReady Studio (devstudio)
  2. JBDS-1593

Detail what 3rd party projects should be included in JBDS 4.x

    XMLWordPrintable

Details

    • Hide
      New 4.1.0.CR2 Extras update site contains BPEL, eGit, FindBugs, Maven (NOT incl. JBoss Maven features - JBDS-1635), Mylyn (but not yet support for JIRA as it doesn't appear to work for Eclipse 3.7 - see subtask: JBDS-1682), PMD, SpringIDE 2.5 (2.6 is included in JBDS 5), Subclipse, and TestNG.

      JBDS 4.1.0 will not include support for Mylyn-JIRA - this is only to be done in 5.x (JBDS-1682).
      Show
      New 4.1.0.CR2 Extras update site contains BPEL, eGit, FindBugs, Maven (NOT incl. JBoss Maven features - JBDS-1635 ), Mylyn (but not yet support for JIRA as it doesn't appear to work for Eclipse 3.7 - see subtask: JBDS-1682 ), PMD, SpringIDE 2.5 (2.6 is included in JBDS 5), Subclipse, and TestNG. JBDS 4.1.0 will not include support for Mylyn-JIRA - this is only to be done in 5.x ( JBDS-1682 ).

    Description

      JBDS 4.0.0 contains:

      • SpringIDE 2.5.1.201011101000-RELEASE
      • TestNG 5.14.6.20110119_1050

      (Hosted here: http://reports.qa.atl.jboss.com/binaries/RHDS/requirements/helios/)

      What should JBDS 4.x contain?

      • SpringIDE 2.5.1.201011101000-RELEASE
      • TestNG 5.14.6.20110119_1050
      • ...?

      Attachments

        1. Screenshot.png
          Screenshot.png
          109 kB
        2. Screenshot-1.png
          Screenshot-1.png
          127 kB
        3. Screenshot-5.png
          Screenshot-5.png
          58 kB
        4. Screenshot-6.png
          Screenshot-6.png
          64 kB

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1836 Relabel "Certified" features as "Selected" to match the actual level of support provided for those add-ons in 4.x

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBDS-1798 Hide 3rd party features from JBDS 4 Extras site - only com.jboss.jbds.* features should be exposed

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBDS-1799 Hide 3rd party features from JBDS 5 Extras site - only com.jboss.jbds.* features should be exposed

          • 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
          clones

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1594 Detail what 3rd party projects should be included in JBDS 5.x

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

          Task - Represents a small unit of work that is not end-user facing. JBDS-1863 Review SpringIDE 2.7.2 for inclusion in JBDS 5

          • 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-1866 Review EGit 1.1 for inclusion

          • 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-1868 Review Indigo SR1 for inclusion

          • 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-1872 Review m2e 1.0.100, m2e-wtp 0.14.0, mavenarchiver 0.15.0 for inclusion in JBT/JBDS

          • 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-1925 Review SpringIDE 2.8.0 for inclusion in JBDS 5

          • 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
          is related to

          Feature Request - Feature requests from customers and/or users JBIDE-8452 JBoss Maven Git integration

          • 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

              manderse@redhat.com Max Andersen
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: