[mojo-dev] [jira] (MCOBERTURA-190) com.ibm.icu:icu:2.6.1 dependency makes maven-enforcer-plugin checkSignatureRule to fail

[Gabriel Belingueres (JIRA)]

Title: Message Title

Gabriel Belingueres commented on an issue   Re: com.ibm.icu:icu:2.6.1 dependency makes maven-enforcer-plugin checkSignatureRule to fail Hi Dennis: You are right, it is not directly related to Cobertura Maven Plugin (CMP), however when checking for java signature compliance (that is, using enforcer plugin) the checking fails due to a transitive dependency that came from CMP, that is icu4j-2.6.1 makes the signature checking to fail (the "Bad class file..." message). Honestly, I don't know if there is something wrong with the icu-2.6.1.jar file or the enforcer plugin, but the workaround I found is to replace the conflicting dependency with a newer one (icu4j-3.4.4 made it). Now, the icu4j dependency came from the jaxen version used in CMP 2.6, but I checked out the 2.7-SNAPSHOT and I see that it is using a newer versions of jaxen, which does not include the icu4j dependency anymore, so maybe the problem is solved for good. Maybe adding an integration test should suffice? Thanks in advance, Gabriel Add Comment   Mojo's Cobertura Maven Plugin / MCOBERTURA-190 com.ibm.icu:icu:2.6.1 dependency makes maven-enforcer-plugin checkSignatureRule to fail When checking signatures for Java 1.6 compatibility in phase "test", the enforcer plugin fails with: {noformat} [INFO] [INFO] --- maven-enforcer-plugin:1.3:enforce (check-signatures) @ ofercap --- [INFO] Checking unresolved references to org.codehaus.mojo.signature:java16:1.1 [ERROR] Bad class file C:\libs\m2-repo\com\ibm\icu\icu4j\2.6.1\icu4j-2.6.... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email