lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Armbrust, Daniel C." <Armbrust.Dan...@mayo.edu>
Subject RE: cvs commit: jakarta-lucene build.xml
Date Wed, 27 Feb 2002 18:17:46 GMT
+ 1 on this Dmitry's votes.


-----Original Message-----
From: Dmitry Serebrennikov [mailto:dmitrys@earthlink.net]
Sent: Wednesday, February 27, 2002 12:09 PM
To: Lucene Developers List
Subject: Re: cvs commit: jakarta-lucene build.xml


As a new and cluless user of Ant, here's my vote:
    +1 on not requiring editing of build.xml
    +1 on keeping default properties in build.xml
    +1 on providing build.properties.sample with comments as to what can 
be overriden and how
    +1 on *no* default.properties

I prefer build.properties.sample to be there because it gives me as a 
cluless user a clear idea as to what to do to customize things. If 
simply default.properties file is there, I wouldn't even think that some 
other file called 'build.properties" could be created to customize 
things (even if after reading the build.xml I could figure out that 
there is an include statement or something). I think having 
default.properties file would confuse things a bit more than required.

The BUILD, COMPILE, or build.readme files can actually explain the fact 
that ant should be used for building, how to customize settings, what 
the ant targets are, how to run ant, and what version of ant is needed.

Dmitry



--
To unsubscribe, e-mail:   <mailto:lucene-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:lucene-dev-help@jakarta.apache.org>

--
To unsubscribe, e-mail:   <mailto:lucene-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:lucene-dev-help@jakarta.apache.org>


Mime
View raw message