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

add m2e features to JBDS Installer

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 5.0.0.M5
    • 5.0.0.M4
    • installer, updatesite
    • None
    • Hide
      m2e features and JBoss Tools features for working with Maven are now on the Core site and included in the installer. Maven is now part of the JBDS ootb experience.

      Not sure if this needs documenting somewhere in the GSG or other doc. Should perhaps note this cosmetic (noisy console log) issue too: https://issues.jboss.org/browse/JBIDE-10339
      Show
      m2e features and JBoss Tools features for working with Maven are now on the Core site and included in the installer. Maven is now part of the JBDS ootb experience. Not sure if this needs documenting somewhere in the GSG or other doc. Should perhaps note this cosmetic (noisy console log) issue too: https://issues.jboss.org/browse/JBIDE-10339
    • Not Yet Documented

    Description

      I'm assuming that this should be done like we do w/ the TestNG and BPEL stuff – simply inject it into the installer:

      https://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse.releng/builders/jbds-all-package/customAssembly.xml

      Alternatively, we could move m2e from Extras to Core.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-10349 build problems in M5

          • 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
          relates to

          Sub-task - The sub-task of the issue JBIDE-10339 after installing JBT Abridged category (including m2e connectors) lots of console errors logged

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

          Task - Represents a small unit of work that is not end-user facing. JBDS-1947 Add org.jboss.tools.maven.jaxrs.feature to JBDS by default

          • 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

              irooskov Isaac Rooskov (Inactive)
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: