You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by jwagenleitner <gi...@git.apache.org> on 2016/07/03 17:35:18 UTC
[GitHub] groovy pull request #363: Security Tests
GitHub user jwagenleitner opened a pull request:
https://github.com/apache/groovy/pull/363
Security Tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jwagenleitner/groovy SecurityTests
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/groovy/pull/363.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 #363
----
commit d53b6d032a4dc4ef94c0c1e6484df040c1db4d47
Author: John Wagenleitner <jw...@apache.org>
Date: 2016-06-30T17:26:39Z
Cleanup Security Tests
Remove code sources from the test policy file and tests
that use scripts that no longer exist or have been moved to
subprojects and are no longer available when testing core.
Remove unused test.
commit 4f85bedcca5b2aa9d5d030809a5d63778e885ac6
Author: John Wagenleitner <jw...@apache.org>
Date: 2016-06-30T22:27:21Z
Fix Security Tests
Adjust policy file settings for new gradle build and ensure
test support class uses privileged access where appropriate.
----
---
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 #363: Security Tests
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/groovy/pull/363
---
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.
---