tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <>
Subject Re: Alternate compilers
Date Mon, 04 Dec 2006 01:12:48 GMT
The IBM problem is likely a compiler bug, since with JSSE 1.0 available, 
those classes should be on the CP.  However, in 5.5, JSSE13SocketFactory is 
never used, so you could just exclude it.  And since it is difficult to use 
TC 3.x and 4.x on JVMs below 1.4, it might be time to get rid of support for 
JSSE 1.0.

The ecj problem looks like a bug in the way that it handles Generics, so 
there isn't much that Tomcat can do about it.

"William L. Thomson Jr." <> wrote in message


 With regard to compiling Tomcat. I just wanted to get a general feel
for how the core Tomcat devs feel about compiling Tomcat with
alternative jdks/compilers.

 Seems there are issues with compiling say Tomcat 5.5.x with ibm jdks,
or when using ecj as the compiler. For example

 Are these issues the Tomcat devs care to resolve? Is Tomcat meant to be
compiled with a specific jdk/compiler like Sun's jdk? Is it looked down
upon to compile tomcat with other jdks? Will they be supported if there
are issues?

 On Gentoo there is lots of choices. One might argue to much, and causes
issues or problems one would not normally run into. More so with Java
apps since even the FOSS Java world has gotten used to shipping and
distributing binaries. I just want to get a better idea of how upstream,
Tomcat devs, feel on this matter.

 From an outside perspective it seems to have deps on sun jdks at times.
Like with regard to Tomcat 6.0.2 seems it does not depend on mx4j/jmx.
Since Sun 1.5 jdks provide that, but others don't have a jmx
implementation. So we will use mx4j as a dep. But that is not how Tomcat
binary will be built, and we will have a deviation there.


William L. Thomson Jr.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message