I have the same problem. Of course setting the
java_home and restarting the cygwin shell does not do
the trick. However, Jikes will not only do the trick
but do it much faster.
just set the compiler to "jikes" just prior to the the
'javac' task.
With jikes.exe in the current dir you will not have a
problem... still looking for a platform neutral way to
share the jikes.exe using a path...
I have yet to test out jikes in production though. The
classic compiler is still very important.
--- Ramesh Donnipadu <[EMAIL PROTECTED]> wrote:
> Hi Berin,
>
> It happened to me once. I defined my JAVA_HOME
> variable to some directory which was
> only a symbolic link to jdk1.2 directory. When I
> changed JAV_HOME to actual
> directory which had jdk1.2, it started working.
>
> If you are using symbolic links, try this approach.
> May be ant does not like
> symbolic links.
>
> Thanks,
> Ramesh
>
>
>
> Berin Loritsch wrote:
>
> > I am running Sun's JDK 1.3.0_01 on Windows 2000.
> >
> > When I run the build.sh file (through cygwin) I
> get
> > the following results:
> >
> > Modern compiler is not available - using classic
> compiler
> > Compiling 102 source files to
> c:\projects\jakarta-ant\build\classes
> >
> > BUILD FAILED
> >
> > Cannot use classic compiler, as it is not
> available A common solution is to set
> > the environment variable JAVA_HOME to your jdk
> directory.
> >
> > This is frustrating. I am trying to update
> junitreport to use Xalan 2
> > but I can't get it to build....
> >
> > I will try without Cygwin, but the distributed
> version of Ant runs against
> > Cygwin. Anybody have some pointers?
>
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
