Re: [jacoco-dev] Options for producing class files with different compilers via Maven

2014-01-09 Thread Evgeny Mandrikov
Indeed, but I missed your point about sources (time to go to bed) and thought that you wanted to duplicate sources. But then it looks good already, isn't it? Or I again missed what embarrasses you in the current solution? On Thu, Jan 9, 2014 at 11:16 PM, Mirko Friedenhagen wrote: > Hello Evgeny

Re: [jacoco-dev] Options for producing class files with different compilers via Maven

2014-01-09 Thread Evgeny Mandrikov
Hi, I have feeling that you ( "we" :) ) could simply use single module and define several executions of: 1. maven-compiler-plugin for compilation 2. maven-assembly-plugin to create JARs and attach them as additional project artifacts But I never tried this. On Thu, Jan 9, 2014 at 10:13

Options for producing class files with different compilers via Maven

2014-01-09 Thread Mirko Friedenhagen
Hello, in the JaCoCo project (a Java code coverage library which uses a Java agent approach during runtime) we produce some false positives of uncovered code because of unreachable (e.g. private constructor of a util class) or synthetic java code (e.g. enum values()). As we inspect the class file