[
https://issues.apache.org/jira/browse/LUCENE-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4570:
----------------------------------
Attachment: LUCENE-4570.patch
de.thetaphi:fobiddenapis:1.0 was released to sonatype release repository.
Attached is the patch to make use of this version 1.0 in Lucene. The patch
still has some TODOs for a later stage, when we should really make the
forbidden-checks per module. As a workaround, Solr checks are currently not so
thourough, because the full classpath is not available on top-level. We can now
also add the check to the Maven build.
I will update the documentation on the project web page tomorrow, while waiting
for the release to be pushed to maven central.
The attached patch already works, as Lucene's IVY config has Sonatype available
as default repository.
> 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, LUCENE-4570.patch, LUCENE-4570.patch,
> LUCENE-4570.patch, 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]
