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

Create JBDS Distribution using productBuild.xml from PDE, P2 director or tycho eclipse-application packaging

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 4.0.0.CR1
    • 4.0.0.Beta2
    • installer
    • None

    Description

      That might be implemented using tycho application packaging or PDE build features.

      It would let us:

      • have any number of JBDS distribution we want (for WEB, SOA and etc development);
      • simplified installer build, because build script would just create installer from JBDS distribution and EAP;
      • no meta info generation during installation required;
      • have only one way to launch JBDS using jbds.exe/jbds/jbds.app platform dependent launcher.
      • change root feature from Eclipse Platform to JBDS and make JBDS real eclipse based product;
      • trigger update for jbds by updating JBDS feature version;
      • control list of available update sites in preferences.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users JBDS-1382 No obvious icon is present to launch JBDS after installation on Mac

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-976 JBDS does not have a branded icon on Mac OS X

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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1363 JBDS 4 upon applying updates loses the JBDS Splash

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1379 Without Win64 installer (incl. Win64 XulRunner + Win64 Eclipse) JBDS installer can't run w/ 64-bit JVM

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1226 Progress Monitor when no server install required is incomplete

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1285 IllegalArgumentException when installing from UNC path on WinXP

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          duplicates

          Feature Request - Feature requests from customers and/or users JBDS-486 improve mechanism for running local builds, including per-module building rather than FULL JBDS/JBT builds

          • 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

          Feature Request - Feature requests from customers and/or users JBDS-857 Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files

          • Optional - The request should be considered desirable but is not an immediate necessity.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1308 replace b3 aggregator w/ tycho update site build

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1350 JBDS should not rebuild/restest included JBT components; instead, aggregate components via b3aggr and p2.repo2runnable

          • 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

              nivologd@gmail.com Denis Golovin (Inactive)
              nivologd@gmail.com Denis Golovin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: