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

rename/refactor JBDS product .feature / plugin / .product to have less confusing names

    XMLWordPrintable

Details

    • Hide

      Steps to Verify:
      1. EXECUTE: Install/Start JBDS
      2. ASSERT: Welcome screen is present
      3. ASSERT: Help -> About JBoss Developer Studio menu is presen
      4. ASSERT: About JBoss Developer Studio Dialog has all JBDS Attributes: Logo image and text
      5. ASSERT: JBDS Icon present in installed features icons list

      Show
      Steps to Verify: 1. EXECUTE: Install/Start JBDS 2. ASSERT: Welcome screen is present 3. ASSERT: Help -> About JBoss Developer Studio menu is presen 4. ASSERT: About JBoss Developer Studio Dialog has all JBDS Attributes: Logo image and text 5. ASSERT: JBDS Icon present in installed features icons list

    Description

      We should consider some better names for these artifacts so they collide less and are more obvious which is which.

      1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/com.jboss.jbds.product.feature/feature.properties

        • featureName=JBoss Developer Studio (Core Features) / BYOE category in update site

      2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/com.jboss.jbds.product/plugin.properties and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/com.jboss.jbds.product/META-INF/MANIFEST.MF

        • Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true

      3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.jboss.jbds.product

        • name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product"

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBDS-2874 Support updating JBDS via BYOE (update site) w/o having to update product too

          • 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 cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3414 remove unneeded p2.inf instructions re: jbds feature refactoring (from 8.0.0)

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3072 Cannot update from JBDS 8.0.0.Beta1 to Beta2

          • 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

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

              Dates

                Created:
                Updated:
                Resolved: