Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. 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

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Major
    • 3.3.0.Beta3
    • 3.3.0.Beta1
    • common
    • None

    Description

      After switching to newer target platform (JBIDE-10289), one test is failing:

      https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--common/606/console
      https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--common/ws/sources/tests/org.jboss.tools.common.verification.test/target/work/data/.metadata/.log/*view*/

      [INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s]

!ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037
!MESSAGE Bundle initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/ was not resolved.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner.notification_4.0.0.
!SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037
!MESSAGE Missing imported package org.junit.runner_4.0.0.

      Guessing the problem is that the test depends on junit4 but the manifest states only junit (not junit4).

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-8838 add source feature to JBT components; generate source plugins w/ Tycho

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

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

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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-10537 Support Code Coverage with Jacoco

          • 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

              mistria@redhat.com Mickael Istria
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: