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

Uwe Schindler edited comment on LUCENE-5055 at 6/13/13 8:34 AM:
----------------------------------------------------------------

bq. With your additional-includes property, can these checks be moved to the 
modules which need it?

-I would keep it like it is for now. By this we automatically do the checks in 
all modules without taking care which actually need them. This would enforce 
the checks.-

I misunderstood! The extra tools check! Yes we can move those checks! Will do 
this.
                
      was (Author: thetaphi):
    bq. With your additional-includes property, can these checks be moved to 
the modules which need it?

I would keep it like it is for now. By this we automatically do the checks in 
all modules without taking care which actually need them. This would enforce 
the checks.
                  
> rat-sources target is missing build and ivy xml files
> -----------------------------------------------------
>
>                 Key: LUCENE-5055
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5055
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: general/build
>            Reporter: Ryan Ernst
>            Assignee: Uwe Schindler
>             Fix For: 5.0, 4.4
>
>         Attachments: LUCENE-5055.patch, LUCENE-5055.patch, LUCENE-5055.patch
>
>
> The check for copyright notices in files isn't checking all files, only 
> source/test files.  A couple modules xml files are missing this (join, 
> spatial, and custom-tasks.xml).

--
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