-
Notifications
You must be signed in to change notification settings - Fork 1.2k
check and merge goal failures in jacoco-maven-plugin with Maven 2.2.1 due to incompatible configuration #129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Googling plugin configuration, I came across this.. http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Mapping_Complex_Objects could this explain the issue with maven 2.2.1 ? This post explains maven plugin configuration was enhanced in maven 3 http://blog.sonatype.com/people/2011/03/configuring-plugin-goals-in-maven-3/#.UomBaRvLO2k hence why test work with maven 3 ? |
|
@muminc Thanks for the links! You're right, probably one has at least to specify the implementation classes. We need to try this as a workaround. |
|
@muminc You are right and this means that at some moment we lost compatibility with Maven 2. |
|
@marchof: maybe we should include a build with Maven 2.2.1 on travis? |
|
@mfriedenhagen I don't think this will help as Travis does not execute tests. We probably need to setup another build at Cloudbees. But before we should probably fix the integration tests for the check goals (if this is possible). |
…he complex type. Does not really help because the version of plexus-container-default used by Maven 2.2.1 does not contain an EnumConverter.
|
Adding implementation for rule is no problem however there is no EnumConverter, so we now get: |
|
I tried to add |
|
Java Code Coverage Tools » jacoco #189 SUCCESS |
|
If I remember correctly Maven can not handle overloaded methods. Have you tried to replace the setElement() method with the string version (instead of adding another one)? |
|
@marchof: I temporarily switched |
* Use String parameters and Enum.valueOf methods because old versions of plexus-container-default used in Maven-2 do not include a EnumConverter. * Add implementation hints in POMs because Maven-2 is unable to guess implementing classes correctly. See http://blog.sonatype.com/people/2011/03/configuring-plugin-goals-in-maven-3/#.UpkF45FIhsp) * Use concrete type ArrayList instead of List in MergeMojo because Maven-2 is not able to deduce a corresponding class for an interface.
…tation hint with Maven-2
* This is needed when you want to compile Jacoco with Maven 2.2.1 because the default maven-compiler-plugin version here assumes JDK1.3 as default. * With Maven 3 the default JDK is 1.5 so buildhive did not detect this.
|
Hello there, with the latest commits all ITs are running fine, I guess you could use the SNAPSHOT for coverage with Maven 2.2.1 again. Only thing outstanding (which is not traced by Travis or BuildHive) is the documentation module which fails with Maven 2.2.1: |
…tation hint with Maven-2.
|
Java Code Coverage Tools » jacoco #191 SUCCESS |
|
@Godin The report generation with Ant seems to be broken with Maven 2. This is something that used to work before, right? |
|
@mfriedenhagen Regarding check goal and merge goal this looks good to me. |
|
@Godin Is it possible to setup another build on cloudbees which runs on Maven 2? Just to make sure we don't get such regressions again. |
|
Strange thing here:
|
Test failures on jacoco-maven-plugin with Maven 2.2.1. The SNAPSHOT produced by the Maven-3 build might be used with Maven 2.2.1 as well. However the complete build of the jacoco project now has another problem with Maven 2, see #164
it-check-passes, it-check-fails-no-halt, it-check-fails-halt:
it-merge-passes-merge: