ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject AW: Override ignored for property java.home
Date Mon, 05 Jul 2004 13:04:02 GMT
> >> > Why is the java.home property defined first.
> >> 
> >> Because it is a system property.
> > 
> > So why can it be changed via console parameters?
> You probably can, but have to ensure you set it as a Java system
> property as well.  ant -Djava.home=foo will try to set an Ant
> property, in order to make it a system property it has to be passed to
> the Java VM and not the Ant Launcher class.  Use the ANT_OPTS
> environment variable to do so.
> No matter whether it actually works or not (I've never tried to
> override an internal property of the Java VM), I'd expect the results
> to be unexpected in many ways.  I haven't followed the start of the
> thread, but I'm afraid that setting java.home programatically is
> either going to do nothing or causes more problems than it solves.

The main thing is: WHY do you want to override java.home?
<java> supports selecting the JVM.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message