[GRADLE-2350] Update from 1.0m5 to 1.0: maven-cobertura-plugin not found Created: 13/Jun/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0
Fix Version/s: None

Type: Bug
Reporter: Marcus Warm Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

Build with 1.0-milestone-5 worked. Build with 1.0 fails:
FAILURE: Build failed with an exception.

  • What went wrong:
    Could not resolve all dependencies for configuration ':xyz:compile'.
    > Artifact 'maven-plugins:maven-cobertura-plugin:1.3@plugin' not found.
  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

I do not use the cobertura-plugin.

dependencies {
compile 'org.seleniumhq.selenium:selenium-server:2.11.0'
compile 'org.seleniumhq.selenium:selenium-firefox-driver:2.11.0'
compile 'org.seleniumhq.selenium:selenium-java:2.11.0'
compile 'org.slf4j:slf4j-log4j12:1.6.4'
compile 'log4j:log4j:1.2.*'
compile 'dom4j:dom4j:1.6.1'
compile 'jaxen:jaxen:1.1.3'
compile 'junit:junit:4.8.1'
compile files("${System.getenv('JAVA_HOME')}/lib/tools.jar")
}

remark: I did not update gradle-wrapper.jar. gradle-1.0[-milestone-5]-bin.jar is in the same folder.

 Comments   
Comment by Marcus Warm [ 13/Jun/12 ]

VERSIONS:

------------------------------------------------------------
Gradle 1.0-milestone-5
------------------------------------------------------------
Gradle build time: Dienstag, 25. Oktober 2011 5.56 Uhr CEST
Groovy: 1.7.10
Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010
Ivy: 2.2.0
JVM: 1.6.0_06 (Sun Microsystems Inc. 10.0-b22)
OS: Windows Vista 6.1 x86

------------------------------------------------------------
Gradle 1.0
------------------------------------------------------------
Gradle build time: Dienstag, 12. Juni 2012 0.56 Uhr UTC
Groovy: 1.8.6
Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010
Ivy: 2.2.0
JVM: 1.6.0_06 (Sun Microsystems Inc. 10.0-b22)
OS: Windows Vista 6.1 x86

Comment by Marcus Warm [ 17/Jun/12 ]

At Home with another Java/Groovy project
I updated from 1.0m7 to 1.0 because of "daemon timeout" problems. The build works. It seems to be faster. No Gradle daemon message.
But then: The EJB3 C/S application does not work anymore.
When starting the desktop client:
"java.lang.VerifyError: Expecting a stackmap frame at branch target 62 in method xy.object.HasId.<clinit>()V at offset 53
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Unknown Source)
at java.lang.Class.getDeclaredField(Unknown Source)
at java.io.ObjectStreamClass.getDeclaredSUID(Unknown Source)
at java.io.ObjectStreamClass.access$700(Unknown Source)
at java.io.ObjectStreamClass$2.run(Unknown Source)
at java.io.ObjectStreamClass$2.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.io.ObjectStreamClass.<init>(Unknown Source)
at java.io.ObjectStreamClass.lookup(Unknown Source)
at java.io.ObjectStreamClass.initNonProxy(Unknown Source)
at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
at java.io.ObjectInputStream.readClassDesc(Unknown Source)
at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
at java.io.ObjectInputStream.readClassDesc(Unknown Source)
at java.io.ObjectInputStream.readClass(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readObject(Unknown Source)
at org.apache.openejb.client.EJBRequest$Body.readMethodParameters(EJBRequest.java:397)
at org.apache.openejb.client.EJBRequest$Body.readExternal(EJBRequest.java:211)
at org.apache.openejb.server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:101)
... 11 more"
Turning back to 1.0m7 and without daemon: build works, application works. Strange! In my opinion something's wrong with 1.0-final.

Comment by Marcus Warm [ 21/Aug/12 ]

cobertura problem:
see http://stackoverflow.com/questions/8295458/maven-failure-to-find-maven-pluginsmaven-cobertura-plugin
The problem is the dependencies in jaxen !

affected versions: 1.0-m8a, 1.1

Comment by Caleb Peter Duke Holt [ 21/Nov/12 ]

I'm also having this problem. I have updated the gradle wrapper in my project to 1.3 so I experienced this problem with 1.0 that I have directly installed on my computer and 1.3 which was the wrapper I used to try again.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:19:30 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.