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

Steven Rowe edited comment on LUCENE-2926 at 2/17/11 11:12 PM:
---------------------------------------------------------------

This patch causes the {{init}} target in {{contrib-build.xml}} to create the 
lucene-core jar if it doesn't exist or if it's out of date 
({{lucene/src/java/\*\*/\*.java}} newer than the jar file).

Without the patch, {{ant build-contrib}} from {{lucene/}} takes 35 seconds 
(best of 3); with the patch, it takes 50 seconds (best of 3).  I think this is 
negligable.

      was (Author: steve_rowe):
    This patch causes the {{init}} target in {{contrib-build.xml}} to create 
the lucene-core jar if it doesn't exist or if it's out of date 
({{lucene/src/java/**/*.java}} newer than the jar file).

Without the patch, {{ant build-contrib}} from {{lucene/}} takes 35 seconds 
(best of 3); with the patch, it takes 50 seconds (best of 3).  I think this is 
negligable.
  
> The "init" target in contrib-build.xml should cause the lucene-core jar to be 
> created
> -------------------------------------------------------------------------------------
>
>                 Key: LUCENE-2926
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2926
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 3.1, 4.0
>            Reporter: Steven Rowe
>            Assignee: Steven Rowe
>            Priority: Minor
>         Attachments: LUCENE-2926.patch
>
>
> It would be helpful (e.g. for simplifying the demo contrib build: 
> LUCENE-2923) if the contribs/modules could depend on the up-to-date existence 
> of the lucene-core jar.

-- 
This message is automatically generated by JIRA.
-
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