[ 
https://issues.apache.org/jira/browse/LUCENE-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576444#comment-13576444
 ] 

Uwe Schindler commented on LUCENE-4570:
---------------------------------------

Hi Steve,

it is a known problem that the Mojo currently cannot handle test classes (I 
think thats documented, unless I missed to add it!). So it is currently not 
supported to change the default phase. I will work on this in a later version - 
the way to go in this case is to have 2 separate Mojos (this is how other 
plugins does it) or like you mentioned, perhaps add a check on the current 
phase. The problem with the latter is: The mojo defines its [dependency 
resolution mode (see 
annotation)|http://maven.apache.org/plugin-tools/maven-plugin-annotations/apidocs/org/apache/maven/plugins/annotations/ResolutionScope.html],
 and this cannot be changed at runtime.

For now, I would only check the main classes (which works without any other 
configuration settings) and leave the tests away.
                
> 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.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]

Reply via email to