On Fri, Feb 22, 2008 at 12:46 PM, Christian Schröder <[EMAIL PROTECTED]> wrote:
> Scot P. Floess wrote:
> > Curious, why don't you just use the 1.5 javac but target 1.4? That
> > should do what you want... I think all you will need to do is this:
>
>
> The problem is that the 1.5 javac won't com
Do you experience the same problem if you by-pass the javac task, and
invoke javac using the exec task?
Obviously not a very nice work-around... but if it solves your
problem :>.
Scot P. Floess wrote:
That's really interesting! To be honest I have not really had a need
to do something l
That's really interesting! To be honest I have not really had a need to
do something like that to date...
I'll have to give this some more thought...
Christian Schröder wrote:
Scot P. Floess wrote:
Curious, why don't you just use the 1.5 javac but target 1.4? That
should do what you want..
Scot P. Floess wrote:
Curious, why don't you just use the 1.5 javac but target 1.4? That
should do what you want... I think all you will need to do is this:
The problem is that the 1.5 javac won't complain if I accidently use
functions from the 1.5 api. It will create a class file which *lo
Curious, why don't you just use the 1.5 javac but target 1.4? That
should do what you want... I think all you will need to do is this:
Christian Schröder wrote:
Hi list,
I have some projects that should be compiled with javac 1.4 and some
that should be compiled with javac 1.5. Since I do
Hi list,
I have some projects that should be compiled with javac 1.4 and some
that should be compiled with javac 1.5. Since I do not want to change my
environment between the projects, I have the JAVA_HOME variable set to
the 1.5 classpath and want ant to use the external 1.4 javac when
necess
