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

Separate JBT and JBDS Central and EA sites

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 4.3.0.Alpha2
    • 4.2.2.Final
    • central-update
    • None

    Description

      Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them.
      This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_guide/8.0/JBT42_Staging_For_QE.adoc#rebuild-target-platforms-for-central-and-early-access ), whereas this is a JBDS need.

      So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS.

      Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-19336 To avoid disparity of versions, Central should not include the same IUs as JBT/JBDS update sites

          • 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

          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) JBIDE-18984 Build Early Access site as an update site, not a TP

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3348 FeedHenry feature isn't available in any JBDS site [9.0]

          • 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-19473 Central can't load Discovery catalog

          • 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-19038 Arquillian should not be in JBT EA catalog

          • 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

              nickboldt Nick Boldt
              mistria@redhat.com Mickael Istria
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: