GitHub user jwagenleitner opened a pull request:

    https://github.com/apache/groovy/pull/427

    Compatibility in 2.4.x with Gradle's classloader cleanup

    Gradle has a cleanup mechanism in place that reflectively accesses
    the ClassInfo.klazz field.  This change prevents an exception being
    thrown by the cleanup method.  This workaround also means that the
    cleanup strategy will no longer work, the fix to replace klazz with a
    WeakReference should eliminate the need for the explicit cleanup.
    
    For more details, see dev mailing list thread:
    
https://mail-archives.apache.org/mod_mbox/incubator-groovy-dev/201609.mbox/%3CCAHPL-JkQ%2BU8PfaxyVhtE%3DvGV%2BsXXmCzxOsCR8UbBww6P2vskPg%40mail.gmail.com%3E

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jwagenleitner/groovy ClassInfoCompat

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/groovy/pull/427.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #427
    
----
commit 81dfa648541f00a33d25bc0084ec240b88c3f321
Author: John Wagenleitner <jwagenleit...@apache.org>
Date:   2016-09-19T18:48:19Z

    Compatibility in 2.4.x with Gradle's classloader cleanup
    
    Gradle has a cleanup mechanism in place that reflectively accesses
    the ClassInfo.klazz field.  This change prevents an exception being
    thrown by the cleanup method.  This workaround also means that the
    cleanup strategy will no longer work, the fix to replace klazz with a
    WeakReference should eliminate the need for the explicit cleanup.
    
    For more details, see dev mailing list thread:
    
https://mail-archives.apache.org/mod_mbox/incubator-groovy-dev/201609.mbox/%3CCAHPL-JkQ%2BU8PfaxyVhtE%3DvGV%2BsXXmCzxOsCR8UbBww6P2vskPg%40mail.gmail.com%3E

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to