On Fri, 17 May 2002, Remy Maucherat wrote:
> Date: Fri, 17 May 2002 10:59:00 -0700
> From: Remy Maucherat <[EMAIL PROTECTED]>
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: Tomcat Developers List <[EMAIL PROTECTED]>
> Subject: Re: Switching javac for jasper 2
>
> > On Fri, 17 May 2002, Kin-Man Chung wrote:
>
> > > > I think the best solution for javac is to just bundle ant.jar and
> > > > use it programmatically ( i.e. new Javac(), etc ). The introspection
> > > > and hacks required to support multiple compilers are just too
> > > > ugly - and they already have good solutions in ant.
> > > >
> > >
> > > I'll look into that. But even if ant.jar is used programmatically,
> > > eventually it still start another process to invoke javac, right? Plus
> > > it's yet another jar to be bundled with tomcat; do we really want
> > > that?
> >
> > Ant doesn't start another process to invoke javac unless you explicitely
> > ask for it ( by fork=true ) or use jikes or another native compiler.
> >
> > Between including 'another jar' that supports most javac compilers and
> > changing the code to support only JDK1.3.1 and JDK1.4 compilers - I
> > think the choice is pretty simple.
>
> I like Costin's solution. Using an abstraction layer for the compiler looks
> to me like a really good idea, as it would allow maximum platform support
> while removing a good chunk of the complexity in Jasper.
>
It's an elegant design idea ... I just hope that having to synchronize the
compiles doesn't cause too many complaints (especially in a development
environment where you are doing this a lot).
> Remy
>
Craig
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
