Uploaded image for project: 'Red Hat CodeReady Studio (devstudio)'
  1. Red Hat CodeReady Studio (devstudio)
  2. JBDS-1773 JBDS50_0470: [DROPPED-COMMIT] (Dev) Support installing JBDS into base Eclipse (was: JBossTools plug-in for Eclipse)
  3. JBDS-2087

move all features from com.jboss.jbds.all (generated top-level product feature) to com.jboss.jbds.product.feature so that all of JBDS can be installed into Eclipse via a single feature

XMLWordPrintable

      A few milestones ago, I moved much of the content of com.jboss.jbds.product.feature into com.jboss.jbds.all to expose it more obviously when a user looks into Help > About > Installation details in JBDS.

      However, this means that the single point of entry to installing all of JBDS is now com.jboss.jbds.all, which, because it's a PRODUCT, can't be installed into something like Eclipse JEE Indigo SR2.

      Solution is to move all the contents of com.jboss.jbds.all into its child feature, com.jboss.jbds.product.feature, and have the .all include ONLY the single .product.feature.

      Any objections to this plan? Denis? Mickael? Max?

        1. eclipse.log.20120413.txt
          8 kB
          Nick Boldt
        2. install-jbds5beta3intoEclipseIndigoSR2JEEbundle.png
          443 kB
          Nick Boldt
        3. JBDS2087.patch.txt
          2 kB
          Nick Boldt
        4. JBDS2087.patch2.txt
          0.9 kB
          Nick Boldt

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

              Created:
              Updated:
              Resolved: