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

ASF GitHub Bot commented on LUCENE-5625:
----------------------------------------

GitHub user greedo opened a pull request:

    https://github.com/apache/lucene-solr/pull/56

    proposed changes LUCENE-5625

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/greedo/lucene-solr trunk

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/lucene-solr/pull/56.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #56
    
----
commit aca11b889f1bca0500c0cec2e218c993884e0fa0
Author: Joe Cabrera <[email protected]>
Date:   2014-06-02T02:41:14Z

    proposed changes LUCENE-5625

----


> Update demo documentation with prerequisites and ant target
> -----------------------------------------------------------
>
>                 Key: LUCENE-5625
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5625
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: general/javadocs, general/website
>    Affects Versions: 4.7.2
>            Reporter: Joe Cabrera
>            Priority: Trivial
>              Labels: documentation
>             Fix For: 4.7.2
>
>         Attachments: LUCENE-5625.patch
>
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> It would be great if the Lucene demo mentioned the fact that Apache Ant and 
> Ivy need to be installed and configured to build the demo JARs. This could be 
> listed in a prerequisites section.
> It might also be a good idea to tell a first time user what ant target to use 
> for building the JARs necessary for the demo.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to