You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pylucene-dev@lucene.apache.org by Andi Vajda <va...@apache.org> on 2012/05/05 03:32:03 UTC
[VOTE] Release PyLucene 3.6.0
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.
Thanks !
Andi..
ps: the KEYS file for PyLucene release signing is at:
http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
http://people.apache.org/~vajda/staging_area/KEYS
pps: here is my +1
Re: [VOTE] Release PyLucene 3.6.0
Posted by Andi Vajda <va...@apache.org>.
On Sun, 6 May 2012, Christian Heimes wrote:
> Am 05.05.2012 23:52, schrieb Andi Vajda:
>> Right. The Lucene error should be clear enough but adding a make target could help. How to communicate that target, though ?
>
> You could either ship ivy with PyLucene and add it to the classpath or
> add this line to the Makefile:
>
> ant ivy-fail || ant ivy-bootstrap
>
> It automatically downloads and install ivy when it's not found.
Cool. I inserted that into the Makefile and rolled a 3.6.0-2 release
candidate.
Thanks !
Andi..
Re: [VOTE] Release PyLucene 3.6.0
Posted by Christian Heimes <ch...@cheimes.de>.
Am 05.05.2012 23:52, schrieb Andi Vajda:
> Right. The Lucene error should be clear enough but adding a make target could help. How to communicate that target, though ?
You could either ship ivy with PyLucene and add it to the classpath or
add this line to the Makefile:
ant ivy-fail || ant ivy-bootstrap
It automatically downloads and install ivy when it's not found.
Christian
AW: [VOTE] Release PyLucene 3.6.0
Posted by Thomas Koch <ko...@orbiteam.de>.
I was able to build JCC and PyLucene - after having fixed the ivy-issue - on
Win7-32 with Python2.7 and Java1.6:
Installed c:\python27\lib\site-packages\jcc-2.13-py2.7-win32.egg
The initial build of PyLucene failed with:
pylucene-3.6.0-1\lucene-java-3.6.0\lucene\common-build.xml:526: The
following error occurred while executing this line:
pylucene-3.6.0-1\lucene-java-3.6.0\lucene\common-build.xml:298: Ivy is not
available
After running the ivy-bootstrap the build went fine.
>cd pylucene-3.6.0-1\lucene-java-3.6.0\lucene
>ant ivy-bootstrap
Buildfile: pylucene-3.6.0-1\lucene-java-3.6.0\lucene\build.xml
ivy-bootstrap:
[mkdir] Created dir: C:\Users\Thomas Koch\.ant\lib
[echo] installing ivy 2.2.0 to C:\Users\Thomas Koch\.ant\lib
[get] Getting:
http://repo1.maven.org/maven2/org/apache/ivy/ivy/2.2.0/ivy-2.2.0.jar
[get] To: C:\Users\Thomas Koch\.ant\lib\ivy-2.2.0.jar
BUILD SUCCESSFUL
Total time: 1 second
Note: running "ant ivy-bootstrap" the 2nd time seems to detect the already
installed version - and not download it again:
ivy-bootstrap:
[echo] installing ivy 2.2.0 to C:\Users\Thomas Koch\.ant\lib
[get] Getting:
http://repo1.maven.org/maven2/org/apache/ivy/ivy/2.2.0/ivy-2.2.0.jar
[get] To: C:\Users\Thomas Koch\.ant\lib\ivy-2.2.0.jar
[get] Not modified - so not downloaded
BUILD SUCCESSFUL
Total time: 1 second
So I'd say either adding "ant ivy-bootstrap" to the "make all" target (of
PyLucene) or simply adding a "make ivy" target (and some hint in the docs)
could help here.
Alternatively it should be clearly marked as a required component to build
PyLucene - as the BUILD readme of java-lucene tells:
> ...Set up your development environment
> (JDK 1.5 or greater, Ant 1.7.1+, Ivy 2.2.0)
However it seems that the ivy.jar in user's local ant dir may not be
sufficient depending on the ANT global config. I understand the Java-Lucene
guys decided to fallback to a wiki page and some error details in the build
process (and declare ivy as required - see above) - cf. lucene jira where
the problem is discussed:
https://issues.apache.org/jira/browse/LUCENE-3946
Finally: my ant-1.8 does not recognize the mentioned "ant --noconfig"
option, but only supports
-nouserlib Run ant without using the jar files from
${user.home}/.ant/lib
-noclasspath Run ant without using CLASSPATH
It's somewhat ironic that bringing in a "very powerful dependency manager"
(Apache Ivy website) results in another dependency issue...
Regards,
Thomas
-----Ursprüngliche Nachricht-----
Von: Andi Vajda [mailto:vajda@apache.org]
Gesendet: Samstag, 5. Mai 2012 23:53
An: pylucene-dev@lucene.apache.org
Betreff: Re: [VOTE] Release PyLucene 3.6.0
>> 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..
Re: [VOTE] Release PyLucene 3.6.0
Posted by Andi Vajda <va...@apache.org>.
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:
Re: [VOTE] Release PyLucene 3.6.0
Posted by Christian Heimes <li...@cheimes.de>.
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.
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: