[
https://issues.apache.org/jira/browse/LUCENE-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580420#comment-13580420
]
Steve Rowe commented on LUCENE-4570:
------------------------------------
bq. I think the executors.txt should be run for both maven main and test
classes. Currently the executors check is only run for main classes, not tests.
Ant build runs it on both. Maybe add the executors next to tests.txt, too.
Ok, I'll do that. I was trying to make the Maven setup the same as the Ant
setup, and missed this difference.
> Release ForbiddenAPI checker on Google Code
> -------------------------------------------
>
> Key: LUCENE-4570
> URL: https://issues.apache.org/jira/browse/LUCENE-4570
> Project: Lucene - Core
> Issue Type: New Feature
> Components: general/build
> Reporter: Robert Muir
> Assignee: Uwe Schindler
> Fix For: 4.2, 5.0
>
> Attachments: LUCENE-4570-maven-inherited.patch,
> LUCENE-4570-maven-inherited.patch, LUCENE-4570-maven.patch,
> LUCENE-4570-maven.patch, 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]
