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 2013/02/05 10:28:19 UTC

[jira] [Resolved] (LUCENE-4570) release policeman tools?

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

Uwe Schindler resolved LUCENE-4570.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 5.0
                   4.2
    
> 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
>             Fix For: 4.2, 5.0
>
>         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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org