[
https://issues.apache.org/jira/browse/LUCENE-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222129#comment-14222129
]
Uwe Schindler commented on LUCENE-6070:
---------------------------------------
Oh, in the current version I cannot disable unresolveable signatures. I have to
wait for a release of bugfix version of forbidden-apis. Unresolveable
signatures can only be disabled in Maven (to allow multi-project builds).
> forbidden-apis fails on Java 9 while parsing deprecated signatures
> ------------------------------------------------------------------
>
> Key: LUCENE-6070
> URL: https://issues.apache.org/jira/browse/LUCENE-6070
> Project: Lucene - Core
> Issue Type: Bug
> Components: general/build
> Affects Versions: Trunk
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: Trunk
>
>
> This is a really new thing:
> This is part of the JDK 8 deprecation list. But this method was actually
> removed in Java 9 completely (the first deprecation ever that was actually
> removed!). This method was deprecated in Java 8 for the first time, with the
> following text:
> "Deprecated. The dependency on PropertyChangeListener creates a significant
> impediment to future modularization of the Java platform. This method will be
> removed in a future release. Applications that need to monitor progress of
> the packer can poll the value of the PROGRESS property instead."
> So I am not sure how to handle that, it seems that in JDK9, Oracle may need
> to remove more deprecated stuff to make modularization possible. In branch_5x
> builds this is not a problem, because it was not deprecated in Java 8, so the
> java 7 signatures file does not have that method listed. A workaround would
> be to enable the forbidden feature to not fail on missing signatures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
