[GRADLE-1516] Daemon buildscript dependency classloader error Created: 06/May/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Marco Hunsicker Assignee: Unassigned
Resolution: Won't Fix Votes: 1

Attachments: Zip Archive gradle-1516.zip    

 Description   

Integrating a 3rd party plugin via a buildscript dependency poses problems when the Gradle daemon is used.

Error:

$ gradle --daemon --stacktrace build
Note: the Gradle build daemon is an experimental feature.
As such, you may experience unexpected build failures. You may need to occasionally stop the daemon.

FAILURE: Build failed with an exception.

  • Where:
    Build file '/home/John Doo/testing/gradle-bug/build.gradle' line: 12
  • What went wrong:
    A problem occurred evaluating root project 'gradle-bug'.
    Cause: java.lang.ExceptionInInitializerError (no error message)
    Cause: plugin.CustomLogger cannot be cast to plugin.CustomLogger

To reproduce:

  • Decompress the archive
  • Switch to "gradle-bug" folder
  • Make sure the daemon is not running:

% gradle --stop

  • Execute the following command 3 times:

% gradle --daemon --stacktrace build

The first time it builds a plugin
The second time the plugin is the first time applied
The third time, the plugin can no longer be applied

 Comments   
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 11:57:29 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.