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

as.core plugin should understand the idea of ESB 4.x instead of needing to explicitly list versions like 4.8,4,9,4.10,4.11,4.12

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • None
    • 4.1.0.Alpha1
    • server
    • None

    Description

      The following JIRAs showcase how ass-backwards the implementation of ESB detection/support in as.core's plugin.xml is:

      JBIDE-13209
      JBDS-2365
      JBDS-2394
      JBDS-1889
      JBDS-2431

      Would it be possible to have the various servers simply support 4.x instead of needing to keep updating as.core's plugin.xml every time a new version of ESB 4.x comes out? (4.11 is currently not supported properly, and 4.12 is forthcoming. Can we make this better in JBDS 7, then maybe backport that magic to JBDS 5 and 6?

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-13356 ESB 4.12+ support in 3.3.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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1889 JBoss ESB runtime check cannot determine correct runtime for SOA-P 5.2.0.ER5 build

          • 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-2431 JBDS5 - Does not recognize ESB 4.11 - deployments to SOA-P servers fail

          • 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-2365 ESB projects cannot be deployed using Server Add/Remove

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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-2394 CLONE - ESB projects cannot be deployed using Server Add/Remove

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

          Task - Represents a small unit of work that is not end-user facing. JBIDE-13209 Need to add ESB 4.12 option with constraints

          • 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

          Activity

            People

              rob.stryker Rob Stryker (Inactive)
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: