On May 5, 2012, at 11:44, Christian Heimes <li...@cheimes.de> wrote:

> Am 05.05.2012 03:32, schrieb Andi Vajda:
>> 
>> The PyLucene 3.6.0-1 release tracking the recent release of
>> Apache Lucene 3.6.0 is ready.
>> 
>> A release candidate is available from:
>> http://people.apache.org/~vajda/staging_area/
>> 
>> A list of changes in this release can be seen at:
>> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_6/CHANGES
>> 
>> 
>> PyLucene 3.6.0 is built with JCC 2.13 included in these release artifacts:
>> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>> 
>> A list of Lucene Java changes can be seen at:
>> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_6_0/lucene/CHANGES.txt
>> 
>> 
>> Please vote to release these artifacts as PyLucene 3.6.0-1.
> 
> Lucene fails to compile because I don't have ivy installed and the
> Makefile doesn't call ivy-bootstrap automatically.

Right. The Lucene error should be clear enough but adding a make target could 
help. How to communicate that target, though ?

Andi..

> 
> Christian
> 
> $ make ANT=ant JCC="python2.7 -m jcc --shared" PYTHON=python2.7 NUM_FILES=4
> cd lucene-java-3.6.0/lucene; ant -Dversion=3.6.0
> Buildfile:
> /home/heimes/dev/py/pylucene_3_6/lucene-java-3.6.0/lucene/build.xml
> 
> check-lucene-core-uptodate:
> 
> compile-lucene-core:
> 
> jflex-uptodate-check:
> 
> jflex-notice:
>     [echo]
>     [echo]       One or more of the JFlex .jflex files is newer than
> its corresponding
>     [echo]       .java file.  Run the "jflex" target to regenerate the
> artifacts.
>     [echo]
> 
> javacc-uptodate-check:
> 
> javacc-notice:
> 
> ivy-availability-check:
>     [echo]
>     [echo]      This build requires Ivy and Ivy could not be found in
> your ant classpath.
>     [echo]
>     [echo]      (Due to classpath issues and the recursive nature of
> the Lucene/Solr
>     [echo]      build system, a local copy of Ivy can not be used an
> loaded dynamically
>     [echo]      by the build.xml)
>     [echo]
>     [echo]      You can either manually install a copy of Ivy 2.2.0 in
> your ant classpath:
>     [echo]        http://ant.apache.org/manual/install.html#optionalTasks
>     [echo]
>     [echo]      Or this build file can do it for you by running the Ivy
> Bootstrap target:
>     [echo]        ant ivy-bootstrap
>     [echo]
>     [echo]      Either way you will only have to install Ivy one time.
>     [echo]
>     [echo]      'ant ivy-bootstrap' will install a copy of Ivy into
> your Ant User Library:
>     [echo]        /home/heimes/.ant/lib
>     [echo]
>     [echo]      If you would prefer, you can have it installed into an
> alternative
>     [echo]      directory using the
> "-Divy_install_path=/some/path/you/choose" option,
>     [echo]      but you will have to specify this path every time you
> build Lucene/Solr
>     [echo]      in the future...
>     [echo]        ant ivy-bootstrap
> -Divy_install_path=/some/path/you/choose
>     [echo]        ...
>     [echo]        ant -lib /some/path/you/choose clean compile
>     [echo]        ...
>     [echo]        ant -lib /some/path/you/choose clean compile
>     [echo]
>     [echo]      If you have already run ivy-bootstrap, and still get
> this message, please
>     [echo]      try using the "--noconfig" option when running ant, or
> editing your global
>     [echo]      ant config to allow the user lib to be loaded.  See the
> wiki for more details:
>     [echo]        http://wiki.apache.org/lucene-java/HowToContribute#antivy
>     [echo]
> 
> ivy-fail:

Reply via email to