[
https://issues.apache.org/jira/browse/SOLR-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885724#action_12885724
]
Hoss Man commented on SOLR-1989:
--------------------------------
This is easily reproducable by trying to run "ant example" from a nightly
download from hudson.
--
In general, the solr build.xml doesn't seem to be looking at the "lucene-libs"
directory consistently. This is particularly noticable if you download a
nightly build artifact from hudson, which only includes the Solr source, and
the lucene+modules dependencies are only available in compiled form.
Running "ant example" or "ant compile-solrj" causes the build to fail with
messages like this...
{noformat}
compile-lucene:
compile-solrj:
[javac] Compiling 89 source files to
/tmp/apache-solr-4.0-2010-07-06_08-06-42/build/solrj
[javac]
/tmp/apache-solr-4.0-2010-07-06_08-06-42/src/common/org/apache/solr/common/util/ConcurrentLRUCache.java:19:
package org.apache.lucene.util does not exist
[javac] import org.apache.lucene.util.PriorityQueue;
...
{noformat}
Running "ant compile" fails even faster, with the "compile-lucene" target being
unable to find the modules...
{noformat}
hoss...@bester:/tmp/apache-solr-4.0-2010-07-06_08-06-42$ ant compile
Buildfile: build.xml
init-forrest-entities:
compile-lucene:
BUILD FAILED
/tmp/apache-solr-4.0-2010-07-06_08-06-42/common-build.xml:212:
/tmp/modules/analysis/common not found.
Total time: 0 seconds
{noformat}
(It's not entirely clear to me what special magic causes "compile-lucene" to
succeed silently when using "ant example" ... a property is getting set
somewhere i'm not seeing)
> Re-Compilation of source needs to be possible in release artifacts
> ------------------------------------------------------------------
>
> Key: SOLR-1989
> URL: https://issues.apache.org/jira/browse/SOLR-1989
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Fix For: 3.1, 4.0
>
>
> Users who download Solr 3.1 or 4.0 should be able to recompile the source -
> at the present moment, this is not possible with nightly builds because of
> assumptions about compiling (and compiling against) .../modules and ../lucene
> -- even though the jars are included in the "lucene-libs" directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
