[
https://issues.apache.org/jira/browse/LUCENE-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557210#comment-13557210
]
Uwe Schindler edited comment on LUCENE-4570 at 1/18/13 1:54 PM:
----------------------------------------------------------------
By the way: The new checker finds use of a deprecated API, that was missing
from the hand-made jdk-deprecated.txt: File.toURL(). Its used at three places
in analyzers - which is a bummer, because it will prevent using those analyzers
on configs where the lucene files are in a directory with e.g. umlauts or other
special symbols (see deprecated message).
Here the message:
{noformat}
-check-forbidden-jdk-apis:
[forbidden-apis] Reading bundled API signatures: jdk-unsafe-1.6
[forbidden-apis] Reading bundled API signatures: jdk-deprecated-1.6
[forbidden-apis] Reading API signatures: C:\Users\Uwe
Schindler\Projects\lucene\trunk-lusolr3\lucene\tools\forbiddenApis\executors.txt
[forbidden-apis] Loading classes to check...
[forbidden-apis] Scanning for API signatures and dependencies...
[forbidden-apis] Forbidden method invocation: java.io.File#toURL() [Deprecated
in Java 1.6]
[forbidden-apis] in
org.apache.lucene.analysis.compound.hyphenation.PatternParser
(PatternParser.java:101)
[forbidden-apis] Forbidden method invocation: java.io.File#toURL() [Deprecated
in Java 1.6]
[forbidden-apis] in
org.apache.lucene.analysis.compound.HyphenationCompoundWordTokenFilter
(HyphenationCompoundWordTokenFilter.java:151)
[forbidden-apis] Forbidden method invocation: java.io.File#toURL() [Deprecated
in Java 1.6]
[forbidden-apis] in
org.apache.lucene.analysis.compound.hyphenation.HyphenationTree
(HyphenationTree.java:114)
[forbidden-apis] Scanned 5468 (and 432 related) class file(s) for forbidden API
invocations (in 2.29s), 3 error(s).
{noformat}
was (Author: thetaphi):
By the way: The new checker finds use of a deprecated API, that was missing
from the hand-made jdk-deprecated.txt: File.toURL(). Its used at three places
in analyzers - which is a bummer, because it will prevent using those analyzers
on configs where the lucene files are in a directory with e.g. umlauts or other
special symbols (see deprecated message).
> release policeman tools?
> ------------------------
>
> Key: LUCENE-4570
> URL: https://issues.apache.org/jira/browse/LUCENE-4570
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Robert Muir
> Assignee: Uwe Schindler
> Attachments: LUCENE-4570.patch
>
>
> Currently there is source code in lucene/tools/src (e.g. Forbidden APIs
> checker ant task).
> It would be convenient if you could download this thing in your ant build
> from ivy (especially if maybe it included our definitions .txt files as
> resources).
> In general checking for locale/charset violations in this way is a pretty
> general useful thing for a server-side app.
> Can we either release lucene-tools.jar as an artifact, or maybe alternatively
> move this somewhere else as a standalone project and suck it in ourselves?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
