[GRADLE-3184] Gradle 2.2-rc-1 regression: codenarcTest fails with NoClassDefFoundError Created: 20/Oct/14  Updated: 24/Jan/17  Resolved: 24/Jan/17

Status: Resolved
Project: Gradle
Affects Version/s: 2.2-rc-1
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Fixed Votes: 0


 Description   

One of our projects fails with the following error:

FAILURE: Build failed with an exception.

  • What went wrong:
    Execution failed for task ':foo:bar:codenarcTest'.
    > java.lang.NoClassDefFoundError: groovy.text.SimpleTemplateEngine

the module in question is using the codenarc plugin:
apply plugin: 'codenarc'

This is the thrown exception: [1]http://pastebin.com/qayff9h3

The same project/module builds fine with Gradle 2.1
----------------------------------------------------------------------------------------
[1] http://pastebin.com/qayff9h3



 Comments   
Comment by Gradle Forums [ 20/Oct/14 ]

Thanks for reporting.

which groovy and codenarc dependencies / versions are you using in your build?

Comment by Gradle Forums [ 20/Oct/14 ]

It will be this change: [1]http://www.gradle.org/docs/release-ca...

Most likely cause is that you are using a transform (perhaps even implicitly) that is doing the wrong thing and trying to load classes.

Would you be able to provide the complete stacktrace (will need to run with `-S`, not `-s`)?. Also, if you can provide a reproducible sample that would be even better.

Thanks for your reliable testing of the RCs once more.
----------------------------------------------------------------------------------------
[1] http://www.gradle.org/docs/release-candidate/release-notes#codenarc-plugin-groovy-version-changes

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 [ 24/Jan/17 ]

I can't reproduce the issue anymore with Gradle 3.3.

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