You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Uwe Schindler (JIRA)" <ji...@apache.org> on 2015/09/12 13:05:46 UTC

[jira] [Updated] (LUCENE-6795) Remove all accessClassInPackage permissions / remove AccessibleObject#setAccessible() to make ready for Java 9 Jigsaw

     [ https://issues.apache.org/jira/browse/LUCENE-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Uwe Schindler updated LUCENE-6795:
----------------------------------
    Summary: Remove all accessClassInPackage permissions / remove AccessibleObject#setAccessible() to make ready for Java 9 Jigsaw  (was: Remove all accessClassInPackage permissions to make ready for Java 9 Jigsaw)

> Remove all accessClassInPackage permissions / remove AccessibleObject#setAccessible() to make ready for Java 9 Jigsaw
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-6795
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6795
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Robert Muir
>              Labels: Java9
>
> With jigsaw builds this stuff is not allowed, its no longer an option of security manager or not.
> So we should remove these permissions and fix the test leaks, crappy code, remove hacks, etc.
> If the hack is really somehow needed for some special reason (e.g. well known case like mmap), it needs to gracefully handle not being able to do this, the code and tests should still "work" if it cannot do the hack.
> Otherwise there will be problems for java 9.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org