You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by Persi <gi...@git.apache.org> on 2017/08/25 06:23:19 UTC

[GitHub] groovy pull request #591: Resource leaks in Groovyc

GitHub user Persi opened a pull request:

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

    Resource leaks in Groovyc

    Building multiple ant projects in a row within the same JVM sometimes fails on windows with locked jars. This is e.g. the case if two build projects has circle dependencies.

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

    $ git pull https://github.com/data-experts/groovy GROOVY_2_5_X

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

    https://github.com/apache/groovy/pull/591.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 #591
    
----
commit 3c7169fa1a4278d2d013a23bb8936b2fd9354bb5
Author: Marcus Berndt <ma...@data-experts.de>
Date:   2017-08-23T09:07:24Z

    Groovyc did not correctly release resources hold by GroovyClassLoader.

commit c7deb9d73e938f884bdb869dab9e78529e0cbfc6
Author: Marcus Berndt <ma...@data-experts.de>
Date:   2017-08-25T06:17:49Z

    Closing the GroovyClassLoader is now realized by try-with-resources.
    
    Old Methode makeCompileUnit is added for API compatibility and marked as deprecated.

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] groovy pull request #591: Resource leaks in Groovyc

Posted by Persi <gi...@git.apache.org>.
Github user Persi closed the pull request at:

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


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---