clover is using java version as 1.4 for some modules

clover is using java version as 1.4 for some modules and 1.8 for some. We have tried setting version in clover-setup property (source="1.8") in build.xml and other workarounds too but no luck. Although if I am putting the source as 1.8 in javac target, it is working fine but that would not be a correct approach.

[clover] Processing files at 1.8 source level.
[clover] Processing files at 1.4 source level.

2 answers

This widget could not be displayed.

What other workarounds have you tried? 

 

What's wrong with setting 1.8 as target source ? Java is mostly backward compatible.

 

I don't think there's an way to tell Clover instrument sources A  with JDK level 4 and sources B with level 8.

The best bet will be to split build process into two parts and compile them in separation. Clover-setup overrides Ant's compiler with its own so I suppose you'd rather would like to use clover-instr target. 

This widget could not be displayed.

Hi Grzegorz,

I have set up the clover instr setting as below and my build is picking it as well, check below screenshot

<clover-instr source="1.8" srcdir="${src.dir}"
destdir="${build.classes.dir}">
</clover-instr>

[clover-instr] Updating existing database at '/data/jenkins/workspace/nk_em-dcc-adapter/.clover/clover.db'.
[clover-instr] Processing files at 1.8 source level.
[clover-instr] Clover all over. Instrumented 158 files (15 packages).
[clover-instr] Elapsed time = 4.121 secs. (38.34 files/sec, 13,515.409 srclines/sec)

 but still java is processing at source level 1.4, please check below

  [clover] Updating existing database at '/data/jenkins/workspace/nk_em-dcc-adapter/.clover/clover.db'.
   [clover] Processing files at 1.4 source level.
   [clover] /data/jenkins/workspace/nk_em-dcc-adapter/em-dcc-omnetric-adapter/src/com/emeter/dcc/ami/adm/setdevice/ConfigureAlertBehaviourHandler.java:95:2:unexpected token: private
   [clover] /data/jenkins/workspace/nk_em-dcc-adapter/em-dcc-omnetric-adapter/src/com/emeter/dcc/ami/adm/setdevice/ConfigureAlertBehaviourHandler.java:95:2:unexpected token: private
   [clover] ** Error(s) occurred and the instrumentation process can't continue.

 Please suggest further.. thanks

Sorry, but I have troubles reading the snippets you provided, are those 2 separate modules or the same one ? According to the DB location it seems like a single build ?

How do you invoke Ant and how do you invoke Clover within Ant build ?  A snippet including whole Clover-related target would be beneficial.
Generally speaking,  It's a common mistake that people use <ant> or <antcall> to call Clover but don't specify inheritrefs=true, therefore Clover config is lost. 

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted yesterday in Statuspage

What are your best incident management tips and stories? #HugOps

 👋Community members! Downtime happens. And great incident response takes a village. Teams like Support, Dev, SRE, Ops, IT, and Marketing have to come together to resolve the problem while keep...

64 views 2 3
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you