On 3/31/02 3:14 PM, "Jon Scott Stevens" <[EMAIL PROTECTED]> wrote:
> on 3/31/02 11:52 AM, "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote: > >> On some platforms. There is no requirement to use configure. > > There is if you want to write easily portable C code. You need to use > automake/autoconf/aclocal... > > FYI, I wrote a large majority of JServ's build system... This is really irrelevant, because you have a set of defaults for configure, and then you generate make files - if we had a system to generate platform specific build.xml files, then I agree with you. But in this case, we have one build.xml, and that is our makefile, so to speak. There are properties that can be *overridden* via a build.properties. But having the defaults external as well is a bit superfluous. It sort of like having the velocity configuration defaults outside of the vel jar and us forcing people to put that file in the classpath too... > >> And there is >> nothing that generates the defaults.properties. > > No need. It is a static file of defaults. :-) For which there is no need either. >> If there was, it could just as well generate the build.properties for the >> user. I think having the ability to be externally generated with something >> like configure would be great - however, it doesn't mean build.xml can't >> have it's own defaults for us primitives that like stuff in one place... > > If you have it in build.xml and default.properties, then it has to be > maintained in two places. > How about an ant target that dumps out the default properties file? Then both problems are solved... One file for maintainability, and then for people who want to override the defaults, it spits out a default.props for them to start with. If you are not overriding anything, there is no need to have this stuff external to build.xml -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting Java : the speed of Smalltalk with the simple elegance of C++... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
