--- Patrick Tullmann <[EMAIL PROTECTED]> wrote:
> > Jetty finds tools.jar itself based on the
> java.home property and
> > adds it to its own classloader. All do some
> checking to see if
> > using the ant.jar directly can do the same thing.
>
> It occurred to me that these tools (ant, jetty,
>
On Sat, Jan 11, 2003 at 01:35:53PM -0700, Patrick Tullmann wrote:
> It occurred to me that these tools (ant, jetty, etc.) are only
> dependent upon a specific class name (i.e., com.sun.tools.javac.Main),
> and what they really want is whatever jar file contains that class.
>
> It seems to me that
> Jetty finds tools.jar itself based on the java.home property and
> adds it to its own classloader. All do some checking to see if
> using the ant.jar directly can do the same thing.
It occurred to me that these tools (ant, jetty, etc.) are only
dependent upon a specific class name (i.e., com.s
Joe Phillips wrote:
Note that jasper2 no longer directly uses tools.jar, as it uses
ant to do all it's compiling. Thus whatever ant.jar needs to find
tools.jar is what jasper and hence tomcat needs.
well, that's good to know that we won't be dependant on tools.jar for
jasper2-using systems.
What
Joe Phillips wrote:
Note that jasper2 no longer directly uses tools.jar, as it uses
ant to do all it's compiling. Thus whatever ant.jar needs to find
tools.jar is what jasper and hence tomcat needs.
well, that's good to know that we won't be dependant on tools.jar for
jasper2-using systems.
On Sat, 2003-01-11 at 10:07, Greg Wilkins wrote:
>
> It is really jasper (the JSP engine from jakarta) that needs
> tools.jar. Tomcat is just one of several servlet containers to
> use jasper.
Right, tomcat was my example. I understand there are other systems that
rely on the java compiler (ant
On Sat, Jan 11, 2003 at 03:07:24PM +, Greg Wilkins wrote:
> Note that jasper2 no longer directly uses tools.jar, as it uses
> ant to do all it's compiling. Thus whatever ant.jar needs to find
> tools.jar is what jasper and hence tomcat needs.
>
> So hopefully the tools.jar dependancy will soo
On Sat, Jan 11, 2003 at 03:07:24PM +, Greg Wilkins wrote:
> Note that jasper2 no longer directly uses tools.jar, as it uses
> ant to do all it's compiling. Thus whatever ant.jar needs to find
> tools.jar is what jasper and hence tomcat needs.
>
> So hopefully the tools.jar dependancy will soo
On Sat, 2003-01-11 at 10:07, Greg Wilkins wrote:
>
> It is really jasper (the JSP engine from jakarta) that needs
> tools.jar. Tomcat is just one of several servlet containers to
> use jasper.
Right, tomcat was my example. I understand there are other systems that
rely on the java compiler (ant
It is really jasper (the JSP engine from jakarta) that needs
tools.jar. Tomcat is just one of several servlet containers to
use jasper.
Note that jasper2 no longer directly uses tools.jar, as it uses
ant to do all it's compiling. Thus whatever ant.jar needs to find
tools.jar is what jasper and he
Hi,
I'm the main developer of the Jetty HTTPServer and Servlet
container and a core developer on JBoss.
Just a reminder (as I've emailed Joe before) that I'm more than
happy to:
+ lobby the JBoss project to make any changes that may
assist you with your packaging (not sure of how successful
Hi,
I'm the main developer of the Jetty HTTPServer and Servlet
container and a core developer on JBoss.
Just a reminder (as I've emailed Joe before) that I'm more than
happy to:
+ lobby the JBoss project to make any changes that may
assist you with your packaging (not sure of how successful
Andrew Pimlott wrote:
But of course people are using it (tools.jar).
That is real life.
But it doesn't solve the problem of whether to use tools.jar
in the first place.
The right question.
Should tools.jar be promoted to a kind of a standard?
Answer: No.
Joe Phillips <[EMAIL PROTECTED]> wrote:
> They should use /etc/alternatives for the name 'tools.jar' if they
> are compatible with Sun's JDK tools.jar.
And make a symlink to $JAVA_HOME/ext ? That way we'll be sure that the
compiler is "automatically" in the [default] classpath... Mayb
Andrew Pimlott wrote:
But of course people are using it (tools.jar).
That is real life.
But it doesn't solve the problem of whether to use tools.jar
in the first place.
The right question.
Should tools.jar be promoted to a kind of a standard?
Answer: No.
--
To UNSUBSCRIBE, email to [E
Joe Phillips <[EMAIL PROTECTED]> wrote:
> They should use /etc/alternatives for the name 'tools.jar' if they
> are compatible with Sun's JDK tools.jar.
And make a symlink to $JAVA_HOME/ext ? That way we'll be sure that the
compiler is "automatically" in the [default] classpath... Mayb
16 matches
Mail list logo
