[ 
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

The forbidden-api checker is now available on sonatype-snapshots with the 
maven-coordinates:
{noformat}
groupId=de.thetaphi
artifactId=forbiddenapis
version=1.0-SNAPSHOT
{noformat}

Attached is a patch for Lucene trunk, removing the forbidden api checker from 
checkout and use the snapshot version. To enable the download of snapshots, I 
added for now (until it is released) the sonatype-snapshots repo to 
ivy-settings.xml.

There is some cleanup needed in the patch:
- It somehow relies on tools compiled, otherwise some properties are not 
defined, to locate the txt files. This can be solved by placing the not-bundled 
lucene-specific signature files outside tools (where its no longer need to be). 
Just place solr ones in solr and lucene ones in lucene.
- I have to review the API files and also move e.g. commons-io.txt to the 
checker JAR file, so we have more bundled signatures and dont need to maintain 
them inside lucene. This of course does not apply to specific solr/lucene ones 
to prevent specific test patterns.

                
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to