Constant_info: invalid tag value

scmuser created the topic: CONSTANT_info: invalid tag value

Hi,

While Doing Instrumentation of jar file, I got following Error…Any help?

[instr] processing instrumentation path ...
    [instr] package [org/w3c/dom] contains classes [DOMException] without full debug info
    [instr] package [org/w3c/tidy] contains classes [AttrCheckImpl$CheckAlign] without full debug info
    [instr] package [org/xml/sax] contains classes [HandlerBase] without full debug info
    [instr] package [com/businessobjects/adv_ivcdzview] contains classes [ApplyQueries] without full debug info
     [echo] build.fail is The following error occurred while executing this line:
     [echo] build_body.xml:1675: java.lang.IllegalStateException: CONSTANT_info: invalid tag value [60]
Tagged :

Com.vladium.emma.EMMARuntimeException

scmuser created the topic: com.vladium.emma.EMMARuntimeException

Hi,
I have J2EE application. Whenever I am trying to instrument my jar file, I am getting following Error…

Any Help on this

com.vladium.emma.EMMARuntimeException: com.vladium.emma.EMMARuntimeException

Tagged :

Instrument class files from all subdirectory

rajeshkumar created the topic: instrument class files from all subdirectory

Hi, is there any possibilities to instrument classes from all sub-directory instead of single class directory? Any sample code?

Regards, Rajesh
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Java.lang.NoClassDefFoundError: com/vladium/emma/rt/RT

rajeshkumar created the topic: “java.lang.NoClassDefFoundError: com/vladium/emma/rt/RT”

I got sometime following error while using emma…

“java.lang.NoClassDefFoundError: com/vladium/emma/rt/RT”

Solution can be found in…

devnet.jetbrains.net/thread/275232
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Ant Example code for Emma Instrumentation and reports

rajeshkumar created the topic: Ant Example code for Emma Instrumentation and reports

In-place instrument a certain subset of already compiled classes using overwrite mode and several coverage filters:

<emma enabled="${emma.enabled}" >
      <instr instrpathref="${out.dir}/classes"
             mode="overwrite"
      >
        <!-- always exclude every class with a "Test" in the name: -->
        <filter excludes="*Test*" />
        <!-- don't instrument everything in "${out.dir}/classes",
             only the stuff I am working on now: -->
        <filter file="myincludes.txt" />
        <!-- additional ANT command line hook: -->
        <filter value="${emma.filter}" />
      </instr>
    </emma>

Don’t overwrite compiled classes that later need to go into official release jars (stay in copy mode). However, use incremental instrumentation for fast personal testing:

<emma enabled="${emma.enabled}" >
          <instr instrpathref="${out.dir}/classes"
                 outdir="${out.dir}/classes-instrumented"
                 merge="yes"
                 filter="${emma.filter}"
          />
    </emma>
 

Take all jars already produced by the product build and make test (coverage-enabled) copies of them:

    <emma enabled="${emma.enabled}" >
          <instr mode="fullcopy"
                 outdir="${out.instr.dir}"
                 merge="no"
                 filter="${emma.filter}"
          >
            <instrpath>
              <fileset dir="${out.dir}" includes="**/*.jar" />
            </instrpath>
          </instr>
    </emma>
 <copy todir="${dist}">
      <fileset dir="${src}"
               includes="**/images/*"
               excludes="**/*.gif"
      />
    </copy>
<copy todir="${dist}">
      <fileset dir="${src}">
        <include name="**/images/*"/>
        <exclude name="**/*.gif"/>
      </fileset>
    </copy>
 

Groups all files in directory ${server.src} that are Java source files and don’t have the text Test in their name.

<fileset dir="${server.src}" casesensitive="yes">
      <include name="**/*.java"/>
      <exclude name="**/*Test*"/>
</fileset>

Groups the same files as the above example, but also establishes a PatternSet that can be referenced in other elements, rooted at a different directory.

<fileset dir="${server.src}" casesensitive="yes">
      <patternset id="non.test.sources">
        <include name="**/*.java"/>
        <exclude name="**/*Test*"/>
      </patternset>
</fileset>
 

Groups all files in directory ${client.src}, using the same patterns as the above example.

<fileset dir="${client.src}" >
  	<patternset refid="non.test.sources"/>
</fileset>

Groups the same files as the top example, but using the selector.

<fileset dir="${server.src}" casesensitive="yes">
  <filename name="**/*.java"/>
  <filename name="**/*Test*" negate="true"/>
</fileset>

Groups the same files as the previous example using a combination of the selector and the selector container.

<fileset dir="${server.src}" casesensitive="yes">
  <filename name="**/*.java"/>
  <not>
    <filename name="**/*Test*"/>
  </not>
</fileset>

Selects all files in src/main

<fileset dir="src" includes="main/" />
 
     	<emma enabled="${emma.enabled}" >
          <instr mode="overwrite" 
          	 instrpath="${jar.location}"
                 destdir="${inst.jar.location}"	
                 metadatafile="${inst.jar.location}/metadata.emma"
                 merge="no" >
            	<instrpath>
              		<fileset dir="${jar.location}" includes="elance-services.jar,web-classes.jar,applet.jar,application-ejb.jar" />
            	</instrpath>
 
         </instr>
      	</emma>
 
 
      	<emma enabled="${emma.enabled}" >
	          <instr mode="fullcopy" 
	          	 instrpath="${jar.location}"
	          	 outdir="${inst.jar.location}"
 
	                 metadatafile="${inst.jar.location}/metadata.emma"
	                 merge="no" >
	            	<instrpath>
	              		<fileset dir="${jar.location}" includes="elance-services.jar,web-classes.jar,applet.jar,application-ejb.jar" />
	            	</instrpath>
 
	         </instr>
      	</emma>
 

Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Cobertura – how to check if class file is instrumented or not?

scmuser created the topic: Cobertura – how to check if class file is instrumented or not?

Hi,

Could you please tell me how to check if class file is instrumented or not using Cobertura?

Tagged :

Npm module “grunt-open” not found. Is it installed?

scmuser created the topic: Npm module “grunt-open” not found. Is it installed?

I am getting following error…

grunt lite
[31m>> [39mLocal Npm module "grunt-open" not found. Is it installed?
Loading "nodestatic.js" tasks...[31mERROR[39m
[31m>> [39mError: Cannot find module 'node-static'
[31m>> [39mLocal Npm module "grunt-contrib-jshint" not found. Is it installed?
[31m>> [39mLocal Npm module "grunt-exec" not found. Is it installed?
[31m>> [39mLocal Npm module "grunt-contrib-copy" not found. Is it installed?
[31m>> [39mLocal Npm module "grunt-contrib-compass" not found. Is it installed?
[31m>> [39mLocal Npm module "grunt-contrib-watch" not found. Is it installed?
[31m>> [39mLocal Npm module "grunt-contrib-symlink" not found. Is it installed?
[31m>> [39mLocal Npm module "grunt-istanbul" not found. Is it installed?
[31m>> [39mLocal Npm module "intern" not found. Is it installed?
Loading "Gruntfile.js" tasks...[31mERROR[39m
[31m>> [39mError: Task "exec:installdeps" not found.
[33mWarning: Task "lite" not found. Use --force to continue.[39m

[31mAborted due to warnings.[39m
Tagged :

Instrumentating class file using Ant in Cobertura

rajeshkumar created the topic: Instrumentating class file using Ant in Cobertura

Instrumentating class file using Ant in Cobertura

Cobertura’s documentation gives the following example to show how instrumentation can be done on classes inside a jar file that is on Cobertura’s classpath.

ANT SCRIPT

<project>
<property name="cobertura.dir" value="../cobertura-2.0.3" />
<property name="instrumented.dir" value="../destination" />
<property name="jars.dir" value="../basedir" />
<property name=" cobertura.datafile " value="../datafile" />


<path id="cobertura.classpath">
<fileset dir="${cobertura.dir}">
<include name="cobertura-2.0.3.jar" />
<include name="lib/**/*.jar" />
</fileset>
</path>



<target name="instrument-classes">
<taskdef classpathref="cobertura.classpath" resource="tasks.properties" />
<delete file="cobertura.ser" />

<cobertura-instrument todir="${instrumented.dir}" datafile="${cobertura.datafile}">
<fileset dir="${jars.dir}">
<include name="XXX.jar" />
</fileset>
<fileset dir="${jars.dir}">
<include name="YYYY.jar" />
</fileset>
</cobertura-instrument>
</target>
</project>

FAQ –
github.com/cobertura/cobertura/wiki/FAQ#…-coverage-everywhere
alvinalexander.com/blog/post/java/sample…ura-ant-build-script
alvinalexander.com/blog/post/best-practi…ertura-code-coverage
stackoverflow.com/questions/12690688/cob…ra-ant-merge-reports
mojo.codehaus.org/cobertura-maven-plugin/cobertura-mojo.html

Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Just to test Order and Unorder list

rajeshkumar created the topic: Just to test Order and Unorder list

First Digit – should be incremented by 1
Second Digit – if its 0, no change but with others digit +3
Third Digit -Should be added +3
Fourth Digit – if 55 then make it 65 and if 56 then make it 66
Rest digit should remain unchanged.
First Digit – should be incremented by 1
Second Digit – if its 0, no change but with others digit +3
Third Digit -Should be added +3
Fourth Digit – if 55 then make it 65 and if 56 then make it 66
Rest digit should remain unchanged.

Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :