[GRADLE-2647] Annotations using the groovy plugin are unable to resolve classes passed to it. Created: 21/Jan/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: tomas lin Assignee: Unassigned
Resolution: Won't Fix Votes: 1


I have the following code example:

package com.example.helloworld;
import javax.ws.rs.*;
import javax.ws.rs.core.MediaType;

public class HelloWorldService{  

This fails compilation using the groovy plugin with the following error message:

Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.sun.ws.rs.ext.RuntimeDelegateImpl ... 17 more Caused by: java.lang.ClassNotFoundException: com.sun.ws.rs.ext.RuntimeDelegateImpl at org.gradle.api.internal.tasks.compile.TransformingClassLoader.findClass(TransformingClassLoader.java:47){pre}

However, it compiles fine once I remove the reference to mediaType and use a String.


The same code compiles fine in maven using the groovy eclipse plugin.

Which leads me to believe that something in the gradle classloaders break groovy compilation.

Our build.gradle file to reproduct this is as follows:

apply plugin: 'groovy'

// Set our project variables
project.ext {
    dropwizardVersion = '0.6.1'

repositories {

dependencies {
    compile group: 'com.yammer.dropwizard', name: 'dropwizard-core', version: dropwizardVersion
    groovy group: 'org.codehaus.groovy', name: 'groovy-all', version: '1.8.7'

A more complete example can be found at https://github.com/tomaslin/dropwizard-gradle/blob/groovy/src/main/groovy/com/example/helloworld/resources/HelloWorldResource.groovy

Comment by Luke Daley [ 21/Jan/13 ]

Is the MediaType type an Enum?

Comment by tomas lin [ 21/Jan/13 ]

No, appears to be a class with static final strings - http://docs.oracle.com/javaee/6/api/javax/ws/rs/core/MediaType.html

Comment by Peter Niederwieser [ 21/Jan/13 ]

See my answer to your question on Stack Overflow.


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:27:37 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.