tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18219] - Can't compile JSP pages
Date Thu, 10 Jul 2003 10:39:48 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18219>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18219

Can't compile JSP pages





------- Additional Comments From john@volano.com  2003-07-10 10:39 -------
I'm going to try to make a case for reopening this bug.  I just lost 2 days to
this problem, so I'm hoping a minor change to the installation program (or
documentation, at least) could prevent the same fate for others.

>From what I can determine, if you're going to run Tomcat 5.0.3 as a Windows
Service, there are no environment variables required whatsoever, nor any PATH
changes, except for one small catch:  you must have JAVA_HOME defined *during*
the Tomcat installation (and only then) if you want your JSP pages to compile.

You don't need it defined /after/ installation, and you don't need it defined
for anything else I've been using for development or production Java tools in
the past 7 years.  In fact, after installation, you don't need anything added to
your PATH at all, and you don't need CATALINA_HOME, ANT_HOME, nor JAVA_HOME defined.

Why have this extra little gotcha in there when Tomcat already knows quite well
where the JDK is installed from the Registry settings?  Furthermore, the
recovery is a bit tough to figure out -- you have to actually uninstall Tomcat,
define JAVA_HOME, and then re-install Tomcat.  Then you can undefine JAVA_HOME
and you're set.  Most of my time lost was because I thought I could recover by
simply defining JAVA_HOME and restarting the Tomcat service.  I didn't imagine
that this environment variable was absolutely critical during the installation
itself.  The rest of the time lost was spent trying all the combinations of the
other environment variables, none of which are required nor helped.

So if the bug won't be reopened, can this message:

  Unable to find a javac compiler;
  com.sun.tools.javac.Main is not on the classpath.
  Perhaps JAVA_HOME does not point to the JDK 

be changed to the following instead?

  Unable to find a javac compiler;
  com.sun.tools.javac.Main is not on the classpath.
  Perhaps you need to define JAVA_HOME and reinstall Tomcat.

Or at least put a big warning in the future Tomcat 5.0 Setup page that says it's
critical for JAVA_HOME to be defined *during* installation when you plan to run
Tomcat 5.0.3 as a Windows Service, but no such Java/Tomcat/Ant environment
variables or PATH changes are required afterwards.

Thanks,
John Neffenger

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message