It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Instrumentation Error

Hi, Recently i faced an error
[INFO] Processing files at 1.6 source level.
[INFO] D:\workspace\trunk\module-project1\src\test\java\com\companyname\TestClassName.java:34:83:expecting '"', found '\n'
[INFO] Instrumentation error
This class can test successful if the command is just mvn test, but error when using

mvn clover2:setup test clover2:aggregate clover2:clover

Could you tell me whiches facats would makes this error?
I am sorry to know what this meanning?(i had tried googling but cannot get helpful options.) Could you help me and forigive my blooper(if it is)...

Maven version: 2.0.9

Java version: 1.6.0_20

The log of error Info(may helps to your concern Info)...

Using the command mvn test

Results :

Tests run: 110, Failures: 0, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------

[INFO] BUILD SUCCESSFUL

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 5 minutes 31 seconds

[INFO] Finished at: Sun Dec 30 16:45:09 2012

[INFO] Final Memory: 7M/17M

[INFO] ------------------------------------------------------------------------

But mvn clover2:setup test clover:aggregate clover2:clover

Results:

[INFO] Scanning for projects...

[INFO] Searching repository for plugin with prefix: 'clover2'.

[INFO] ------------------------------------------------------------------------

[INFO] Building Unnamed - pj-t:jar:1.7.0

[INFO] task-segment: [clover2:setup, test]

[INFO] ------------------------------------------------------------------------

[INFO] [clover2:setup]

[INFO] No 'maven.clover.licenseLocation' configured. Using default evaluation license.

[INFO] No Clover instrumentation done on source files in: [D:\workspace\trunk\pj-t\src\main\java] as no matching sources

files found

[INFO] Clover Version 3.1.8, built on November 13 2012 (build-876)

[INFO] Loaded from: M:\local_responsty\com\cenqua\clover\clover\3.1.8\clover-3.1.8.jar

[INFO] Clover Evaluation License registered to Clover Maven Plugin.

[INFO] You have 29 day(s) before your license expires.

[INFO] Updating existing database at 'D:\workspace\trunk\pj-t\target\clover\clover.db'.

[INFO] Processing files at 1.6 source level.

[INFO] D:\workspace\trunk\pj-t\src\test\ClassNameTest.java:34:83:expecting '"', found '\n'

[INFO] Instrumentation error

com.atlassian.clover.api.CloverException: D:\workspace\trunk\pj-t\src\test\ClassNameTest.java:34:83:expecting '"', found '\n'

at com.atlassian.clover.instr.java.Instrumenter.instrument(Instrumenter.java:169)

at com.cenqua.clover.CloverInstr.execute(CloverInstr.java:73)

at com.cenqua.clover.CloverInstr.mainImpl(CloverInstr.java:49)

at com.atlassian.maven.plugin.clover.internal.instrumentation.AbstractInstrumenter.instrumentSources

(AbstractInstrumenter.java:194)

at com.atlassian.maven.plugin.clover.internal.instrumentation.AbstractInstrumenter.instrument

(AbstractInstrumenter.java:72)

at com.atlassian.maven.plugin.clover.CloverInstrumentInternalMojo.execute(CloverInstrumentInternalMojo.java:347)

at com.atlassian.maven.plugin.clover.CloverSetupMojo.execute(CloverSetupMojo.java:31)

at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures

(DefaultLifecycleExecutor.java:330)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)

at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)

at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

Caused by: line 34:83: expecting '"', found '\n'

at com.atlassian.clover.instr.java.JavaLexer.nextToken(JavaLexer.java:445)

at com.atlassian.clover.instr.java.UnicodeJavaLexer.nextToken(UnicodeJavaLexer.java:60)

at cloverantlr.TokenStreamHiddenTokenFilter.consume(TokenStreamHiddenTokenFilter.java:38)

at cloverantlr.TokenStreamHiddenTokenFilter.nextToken(TokenStreamHiddenTokenFilter.java:134)

at com.atlassian.clover.instr.java.CloverTokenStreamFilter.nextToken(CloverTokenStreamFilter.java:160)

at cloverantlr.TokenBuffer.fill(TokenBuffer.java:69)

at cloverantlr.TokenBuffer.LA(TokenBuffer.java:80)

at cloverantlr.LLkParser.LA(LLkParser.java:52)

at com.atlassian.clover.instr.java.JavaRecognizer.statement(JavaRecognizer.java:2437)

at com.atlassian.clover.instr.java.JavaRecognizer.compoundStatement(JavaRecognizer.java:3028)

at com.atlassian.clover.instr.java.JavaRecognizer.handler(JavaRecognizer.java:3409)

at com.atlassian.clover.instr.java.JavaRecognizer.tryCatchBlock(JavaRecognizer.java:3232)

at com.atlassian.clover.instr.java.JavaRecognizer.statement(JavaRecognizer.java:2716)

at com.atlassian.clover.instr.java.JavaRecognizer.outerCompoundStmt(JavaRecognizer.java:2248)

at com.atlassian.clover.instr.java.JavaRecognizer.field(JavaRecognizer.java:1850)

at com.atlassian.clover.instr.java.JavaRecognizer.classBlock(JavaRecognizer.java:1453)

at com.atlassian.clover.instr.java.JavaRecognizer.classDefinition(JavaRecognizer.java:652)

at com.atlassian.clover.instr.java.JavaRecognizer.typeDefinition2(JavaRecognizer.java:582)

at com.atlassian.clover.instr.java.JavaRecognizer.typeDefinition(JavaRecognizer.java:443)

at com.atlassian.clover.instr.java.JavaRecognizer.compilationUnit(JavaRecognizer.java:364)

at com.atlassian.clover.instr.java.Instrumenter.instrument(Instrumenter.java:220)

at com.atlassian.clover.instr.java.Instrumenter.instrument(Instrumenter.java:126)

... 24 more

[INFO] ------------------------------------------------------------------------

[ERROR] BUILD ERROR

[INFO] ------------------------------------------------------------------------

[INFO] Clover has failed to instrument the source files in the [D:\workspace\trunk\pj-t\target\clover\src-test-instrumented]

directory

[INFO] ------------------------------------------------------------------------

[INFO] For more information, run Maven with the -e switch

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 6 seconds

[INFO] Finished at: Thu Dec 27 21:47:22 2012

[INFO] Final Memory: 10M/26M

[INFO] ------------------------------------------------------------------------

While, the config file is correct(i test in other project and it run).

Thanks a lot!

edward

3 answers

1 accepted

0 votes
Answer accepted
Hi, Jacek The problem resolved...it seems that the encode's problem... Changed the config file likes below: <groupid>com.atlassian.maven.plugins</groupid> <artifactid>maven-clover2-plugin</artifactid> <configuration> <encoding>utf-8</encoding> Then the error will disappear... Thanks for Marek's help... Thanks a lot!

Hi Edward,

What Clover version do you use?

In order to help you I need to get the TestClassName.java source file and its dependencies.
The best would be if you open Clover support request at http://support.atlassian.com. We could share source code there and other private data in a secure way.

Thanks,
Jacek

Clover Version 3.1.8, built on November 13 2012 (build-876)

Hi Jaroczynski,

Our project is very big and because my company's rule, i cannot use source code. I will emulate a simple code to test clover(this will wast some time...), if the same error occur i will told you at first time. Thanks very much, Jaroczynski.

cheers

Edward

[INFO] Clover Version 3.1.8, built on November 13 2012 (build-876)

Hi Jaroczynski,

Our project is very big and because my company's rule, i cannot use source code. I will emulate a simple code to test clover, if the same error occur i will told you at first time. Thanks very much, Jaroczynski.

cheers

Edward

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

What's New in Confluence Cloud – November 2019 Edition

Hey community! This month we’re excited to share brand new features to help you make your mark on Confluence. If you haven’t already, check out our updates from October and September too! Expre...

30,055 views 29 57
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you