[Monetdb-developers] [Monetdb-pf-checkins] pathfinder/src/tools/java build.properties, XQuery_0-20, 1.1.2.3, 1.1.2.4

Fabian Groffen Fabian.Groffen at cwi.nl
Thu Nov 1 17:24:31 CET 2007


On 01-11-2007 13:28:22 +0100, Sjoerd Mullender wrote:
> Fabian Groffen wrote:
> > On 01-11-2007 10:48:18 +0000, Ying Zhang wrote:
> >> Update of /cvsroot/monetdb/pathfinder/src/tools/java
> >> In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv5671
> >>
> >> Modified Files:
> >>       Tag: XQuery_0-20
> >> 	build.properties 
> >> Log Message:
> >> Corrected value of the "compiler" attribute of <javac>
> > [snip]
> >>  # which Java compiler to use, default: javac
> >> -build_compiler=javac
> >> +build_compiler=javac1.5
> > 
> > While the comment doesn't reflect a valid state here, this isn't too
> > flexible.  Why don't you just drop the whole build_compiler variable you
> > introduced, and use the completely transparent and well supported and
> > usually expected build.compiler variable only once you really want to
> > control what compiler is being used, as I suggested to you earlier?
> 
> I don't know all the implications, but it seems to me that you should
> *not* specify the compiler in the build.{xml,properties} files.  Just
> use whatever the system provides.  On at least both Fedora and Cygwin it
> is possible to switch Java using the alternatives program (as
> superuser).  And you should be able to change your $PATH to switch
> compilers.

Absolutely true.  That's why Jennie should remove her build_compiler
variable and all its trails from her entire Java project.

Repeating myself again, if you want ant to use another compiler, set
build.compiler in build.local.properties, or give it as argument to ant
during it's invocation.




More information about the developers-list mailing list