I looked at this code yesterday and was confused, too. Common-build.xml 
currently reads the build properties only from the "lucene/"  directory (which 
is common.dir) or from the working directory of the actually processed 
build.xml file (base.dir). We might change this (I was about to do this), 
because I added support for the smoketester sitting in the root folder (which 
ignored the properties file). We should fix this in a separate folder, so 
common-build.xml reads from home dir or *only* the root folder of lucene/solr.

The most simple thing is to place a file "lucene.build.properties" in your 
$HOME (~) directory. This is how I have it set up. Build.properties would also 
work, but this is most sepcfic and would work for every Lucene checkout you are 
working on. 

Uwe

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [email protected]


> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf
> Of Dawid Weiss
> Sent: Thursday, March 13, 2014 4:14 PM
> To: [email protected]
> Subject: Re: Stalled unit tests
> 
> The "root" of the project meaning Solr and Lucene codebase? Yeah... I don't
> think it'll work. Lucene and Solr still try to separate their codebases, even 
> if
> there is a single SVN root.
> 
> Dawid
> 
> On Thu, Mar 13, 2014 at 3:59 PM, Terry Smith <[email protected]> wrote:
> > Dawid,
> >
> > Thanks, I didn't even know about it until Mike mentioned it earlier in
> > this thread. I've had it work from ~/lucene.build.properties and
> > ~/build.properties but didn't have any luck putting it in the root of
> > project (I'm probably just miss reading the ant file).
> >
> > --Terry
> >
> >
> >
> > On Thu, Mar 13, 2014 at 9:35 AM, Dawid Weiss
> > <[email protected]>
> > wrote:
> >>
> >> Terry,
> >>
> >> The build.properties file holds the current user's config, as opposed
> >> to the defaults stored in the repository. In fact, there are more
> >> locations where you can put such defaults (see common-build.xml's
> >> header):
> >>
> >>   <!-- Give user a chance to override without editing this file
> >>       (and without typing -D each time it compiles it -->
> >>   <property file="${user.home}/lucene.build.properties"/>
> >>   <property file="${user.home}/build.properties"/>
> >>   <property file="${basedir}/build.properties"/>
> >>   <property file="${common.dir}/build.properties"/>
> >>
> >>
> >> Dawid
> >>
> >> On Thu, Mar 13, 2014 at 2:29 PM, Terry Smith <[email protected]>
> wrote:
> >> > It seems that you need to run the tests with
> >> > `-Dtests.disableHdfs=true` for them to succeed. Is there any
> >> > interested in making this the default behavior?
> >> >
> >> > If not, I'll happily start a new email thread to get wiki
> >> > permissions so that the contribution pages linked from the main
> >> > README.txt will both mention this important flag.
> >> >
> >> > http://wiki.apache.org/lucene-java/HowToContribute
> >> > http://wiki.apache.org/solr/HowToContribute
> >> >
> >> >
> >> > Right now they both state that you can run `ant clean test`,
> >> > unfortunately that command will fail if you run the tests from
> >> > either the top level of the project or the solr subdirectory unless
> >> > you instead run `ant -Dtests.disableHdfs=true clean test` or create
> >> > a build.properties file.
> >> >
> >> > I also couldn't find any references to build.properties on the
> >> > wiki, here are the searches I tried:
> >> >
> >> >
> >> > http://wiki.apache.org/general/FrontPage?action=fullsearch&context=
> >> > 180&value=build.properties&fullsearch=Text
> >> >
> >> >
> http://www.google.com/?q=%22build.properties%22+site:wiki.apache.or
> >> > g%2Flucene
> >> >
> >> >
> http://www.google.com/?q=%22build.properties%22+site:wiki.apache.or
> >> > g%2Fsolr
> >> >
> >> >
> >> > Is this documented somewhere else? I'd be happy to back some out
> >> > from the ant files, collate documentation from other sources and
> >> > make it easier to find.
> >> >
> >> > --Terry
> >> >
> >> >
> >> > On Mon, Mar 10, 2014 at 2:55 PM, Dawid Weiss
> >> > <[email protected]>
> >> > wrote:
> >> >>
> >> >> > Dawid: Boy, those are some large timeouts!
> >> >>
> >> >> I know... I wasn't the one to bump them; my default was, I think,
> >> >> about 3 minutes per class...
> >> >>
> >> >> Dawid
> >> >>
> >> >> ------------------------------------------------------------------
> >> >> --- To unsubscribe, e-mail: [email protected] For
> >> >> additional commands, e-mail: [email protected]
> >> >>
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected] For
> >> additional commands, e-mail: [email protected]
> >>
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected] For additional
> commands, e-mail: [email protected]


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

Reply via email to