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

Seam 2 is still included in JBDS 9 Alpha1 installed from jar

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 9.0.0.Alpha2
    • 9.0.0.Alpha1
    • build, cdi, seam
    • None
    • NEW

    Description

      It seems to me that we removed the wrong feature.

      This is JBDS 8.0.2:

      nattura:features rasp$ ls |grep seam
org.jboss.tools.cdi.seam.feature_1.6.1.Final-v20141209-0505-B79
org.jboss.tools.maven.seam.feature_1.6.1.Final-v20150109-2320-B116
org.jboss.tools.runtime.seam.detector.feature_3.6.1.Final-v20141209-0505-B79
org.jboss.tools.seam.feature_3.6.1.Final-v20141209-0505-B79

      And this is JBDS 9.0.0.Alpha1 B11:

      nattura:features rasp$ ls |grep seam
org.jboss.tools.seam.feature_3.7.0.Alpha1-v20150213-0551-B3

      When you look at plugins, it looks as follows:
      JBDS 8.0.2:

      nattura:plugins rasp$ ls|grep seam
org.jboss.tools.cdi.seam.config.core_1.6.1.Final-v20141209-0505-B79.jar
org.jboss.tools.cdi.seam.config.ui_1.6.1.Final-v20141209-0505-B79.jar
org.jboss.tools.cdi.seam.core_1.6.1.Final-v20141209-0505-B79.jar
org.jboss.tools.cdi.seam.faces.core_1.6.1.Final-v20141209-0505-B79.jar
org.jboss.tools.cdi.seam.solder.core_1.6.1.Final-v20141209-0505-B79.jar
org.jboss.tools.cdi.seam.text.ext_1.6.1.Final-v20141209-0505-B79.jar
org.jboss.tools.jsf.vpe.seam_3.6.1.Final-v20141209-0505-B79
org.jboss.tools.maven.seam_1.6.1.Final-v20150109-2320-B116.jar
org.jboss.tools.runtime.seam.detector_3.6.1.Final-v20141209-0505-B79.jar
org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar
org.jboss.tools.seam.pages.xml_3.6.1.Final-v20141209-0505-B79.jar
org.jboss.tools.seam.text.ext_3.6.1.Final-v20141209-0505-B79.jar
org.jboss.tools.seam.ui.pages_3.6.1.Final-v20141209-0505-B79.jar
org.jboss.tools.seam.ui_3.6.1.Final-v20141209-0505-B79.jar
org.jboss.tools.seam.xml.ui_3.6.1.Final-v20141209-0505-B79.jar
org.jboss.tools.seam.xml_3.6.1.Final-v20141209-0505-B79.jar

      JBDS 9.0.0.Alpha1 B11:

      nattura:plugins rasp$ ls|grep seam
org.jboss.tools.cdi.seam.solder.core_1.7.0.Alpha1-v20150213-0551-B3.jar
org.jboss.tools.jsf.vpe.seam_3.7.0.Alpha1-v20150213-0551-B3
org.jboss.tools.seam.core_3.7.0.Alpha1-v20150213-0551-B3.jar
org.jboss.tools.seam.pages.xml_3.7.0.Alpha1-v20150213-0551-B3.jar
org.jboss.tools.seam.text.ext_3.7.0.Alpha1-v20150213-0551-B3.jar
org.jboss.tools.seam.ui.pages_3.7.0.Alpha1-v20150213-0551-B3.jar
org.jboss.tools.seam.ui_3.7.0.Alpha1-v20150213-0551-B3.jar
org.jboss.tools.seam.xml.ui_3.7.0.Alpha1-v20150213-0551-B3.jar
org.jboss.tools.seam.xml_3.7.0.Alpha1-v20150213-0551-B3.jar

      For JBoss Tools, both are there (seam and cdi.seam) - I'm not sure if that's intentional. Is there a JIRA for dropping seam?

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-19316 Portlet Tools shouldn't have a hard dependency on Seam

          • 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 JBDS-3286 Remove Seam tooling from default JBDS installation

          • 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. JBDS-3341 JBDS 9.0 installer drops by ~60M & update site by ~300M vs. 8.1 sizes

          • 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. JBIDE-19645 Remove seam 3 features from JBDS install

          • 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. JBIDE-19646 Move org.jboss.tools.jsf.vpe.seam into the Seam module

          • 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

          Feature Request - Feature requests from customers and/or users JBDS-3286 Remove Seam tooling from default JBDS installation

          • 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-19401 remove Seam & Portlet from JBT 4.3 default install

          • 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. JBIDE-19608 For JBIDE 4.3.0.Alpha2: Code Freeze + Branch

          • 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

          Activity

            People

              fbricon@redhat.com Fred Bricon
              exd-mmalina Martin Malina
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: