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

build problems in Beta3

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 3.3.0.Beta3
    • 3.3.0.Beta3
    • build, updatesite
    • None

    Description

      Container issue for build problems w/ Beta3. Check subtasks & links for component-specific issues.

      Attachments

        Issue Links

          clones

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

          • 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
          is blocked by

          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

          Feature Request - Feature requests from customers and/or users JBIDE-10659 Investigate use of m2e-wtp 0.15.1 in JBDS 5, JBoss Central, target platforms & composite reqs mirror

          • 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

          Feature Request - Feature requests from customers and/or users JBIDE-10834 Investigate use of m2e-jdt-compiler 1.0.0 in composite reqs mirror (but not JBDS 5 Extras, JBoss Central or target platforms)

          • 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-2000 Ain't no party like a JBoss party

          • 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. JBIDE-11278 compile failed in hibernate

          • 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. JBIDE-11701 JBT nightly aggregation build failures

          • 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. JBIDE-11718 compile failed in openshift

          • 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-1956 get m2eclipse logging under control in JBDS

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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1949 JBoss logo is a button for launching a server, a button for Central, an editor icon, and IN the editor too: confusing overkill?

          • 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-2008 JBDS from trunk - dependency issues with corresponding SOA tooling

          • 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-10276 test failures in org.jboss.tools.maven.ui.bot.test

          • 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-10277 test failure in org.hibernate.eclipse.console.test

          • 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-10289 create composite reqs site for Indigo SR2

          • 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-10796 remove org.eclipse.pde.api.tools.ee.fragments from target platforms

          • 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-10950 use seam 2.2.1.Final instead of 2.2.1.CR1 and 2.2.1.CR2 in requirements?

          • 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-11600 Implement a meaningful Test for tests/ module, instead of org.jboss.tools.tests.tests.UtilsTest

          • 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 cloned by

          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

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-10529 com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime version of class [org.jboss.tools.common.util.****] in the coverage data is not consistent with the version of this class in the metadata, possibly because stale metadata

          • 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
          1.
          		 compile failed in as.ui :: The method setErrorMessage(String) of type DeploymentTypeUIUtil.NewServerWizardBehaviourCallback must override a superclass method Sub-task Closed Major Rob Stryker (Inactive)
          2.
          		 test failures in CDI - SWT No More Handles Sub-task Closed Major Alexey Kazakov
          3.
          		 test failures in Common Sub-task Closed Major Alexey Kazakov
          4.
          		 test failures in ESB Sub-task Closed Major Brian Fitzpatrick (Inactive)
          5.
          		 test failures in jbpm - SWT No More Handles Sub-task Closed Major Koen Aers
          6.
          		 test failures in JSF Sub-task Closed Major Victor Rubezhny (Inactive)
          7.
          		 test failures in Seam Sub-task Closed Major Alexey Kazakov
          8.
          		 test failures in VPE - SWT No More Handles Sub-task Closed Major Yahor Radtsevich (Inactive)
          9.
          		 RHEL6 slaves fail to run SWT-based tests Sub-task Closed Major Nick Boldt
          10.
          		 no code coverage found for JSF builds Sub-task Closed Major Denis Golovin (Inactive)
          11.
          		 SOA Tooling .tests & .continuous jobs are misconfigured: profiles not found, no tests run Sub-task Closed Major Nick Boldt
          12.
          		 tests component job not archiving correctly Sub-task Closed Major Mickael Istria
          13.
          		 test timeout after 1800 seconds in org.jboss.tools.ws.jaxrs.core.test Sub-task Closed Major Xavier Coulon
          14.
          		 test failure in org.jboss.ide.eclipse.as.test.publishing.v2.JSTDeployBinaryChildModuleTest.testJBoss7BinaryChildDeployment (from org.jboss.ide.eclipse.as.test.ASTestSuite) Sub-task Closed Major Rob Stryker (Inactive)
          15.
          		 internmittent test failures in org.jboss.tools.central.test.JBossCentralAllTests Sub-task Closed Major Snjezana Peco (Inactive)
          16.
          		 jbosstools-3.3_stable_branch.tests is running out of memory (heap) Sub-task Closed Major Mickael Istria
          17.
          		 jbosstools-3.3_stable_branch.continuous failing to compile -- java.lang.OutOfMemoryError: GC overhead limit exceeded Sub-task Closed Blocker Mickael Istria
          18.
          		 something is looking for GWT 2.6, but 2.5.1 is on TP and composite reqs site Sub-task Closed Major Denis Golovin (Inactive)

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: