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

improve mechanism for running local builds, including per-module building rather than FULL JBDS/JBT builds

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Won't Do
    • Major
    • None
    • LATER
    • build
    • None

    Description

      To run a component build locally, you need only do this:

      cd /tmp; svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/build/
      or
      cd /tmp; svn co http://anonsvn.jboss.org/repos/jbosstools/branches/modular_build/build/

      then

      cd /tmp/build; ant -DCOMPONENTS=tests,common,jmx

      If you want to build from workspace sources, do the same above but from within your workspace. Simple!

      For examples on using the build script, or the order of components to build, do:

      cd /tmp/build; ant help

      Attachments

        Issue Links

          incorporates

          Task - Represents a small unit of work that is not end-user facing. JBIDE-4319 Include jbpm4 into 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
          is blocked by

          Feature Request - Feature requests from customers and/or users JBIDE-3191 Cannot run tests when building JMX by itself

          • 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

          Feature Request - Feature requests from customers and/or users JBDS-487 make ui tests run on a different UI thread (eg., using xvfb) so they can run locally without accidental user interaction

          • 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. JBIDE-6304 org.jboss.tools.test.util.ResourcesUtils.importProject should understand how to unjar a plugin (Tycho build/test requirement)

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-6410 org.jboss.ide.eclipse.archives.test stalls build for hours

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBDS-464 Get rid of two copies of eclipse in jbds-build/eclipse and jbds-build/clean-eclipse in 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
          is duplicated by

          Task - Represents a small unit of work that is not end-user facing. JBDS-1351 Create JBDS Distribution using productBuild.xml from PDE, P2 director or tycho eclipse-application packaging

          • 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
          There are no Sub-Tasks for this issue.

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: