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

Steve Rowe commented on LUCENE-4570:
------------------------------------

bq. Looks good, I only dont like the repeated code in every module. Maybe we 
can improve that later.

Yeah, I don't like it either, but Maven doesn't have a directly supported way 
to find the base directory in a multi-module build; this is required to locate 
the rule files.  

I looked around the web for solutions today, and I two possible alternatives to 
the technique I use (i.e.: have each module define its own {{$\{top-level\}}} 
property pointing to the project base directory in relative terms):

# package resources into a jar on which each sub-module depends; the plugin can 
then extract resources from the jar
# use an embedded groovy script to set recursively find the project base 
directory, then set a property containing the absolutized directory.

I *think* I've tried #2 in the past, but I'll try again.
                
> 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-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