You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/07/19 09:29:02 UTC
DO NOT REPLY [Bug 16688] -
JSP's not compiling - javac: invalid flag: C:\Java\jars\Tomcat
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=16688>.
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=16688
JSP's not compiling - javac: invalid flag: C:\Java\jars\Tomcat
hauser@acm.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hauser@acm.org
URL| |http://jakarta.apache.org/to
| |mcat/faq/misc.html#compile
Summary|JSP's not compiling |JSP's not compiling -
| |javac: invalid flag:
| |C:\Java\jars\Tomcat
------- Additional Comments From hauser@acm.org 2003-07-19 07:29 -------
I have the same problem with a different spin to it:
In the browser, I see
<<org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: -1 in the jsp file: null
Generated servlet error:
[javac] Since fork is true, ignoring compiler setting.
[javac] Compiling 1 source file
[javac] Since fork is true, ignoring compiler setting.
[javac] javac: invalid flag: C:\Java\jars\Tomcat
[javac] Usage: javac
[javac] where possible options include:
[javac] -g Generate all debugging info
[javac] -g:none Generate no debugging info
[javac] -g:{lines,vars,source} Generate only some debugging info
[javac] -nowarn Generate no warnings
[javac] -verbose Output messages about what the compiler
is doing
[javac] -deprecation Output source locations where deprecated
APIs are used
[javac] -classpath Specify where to find user class files
[javac] -sourcepath Specify where to find input source files
[javac] -bootclasspath Override location of bootstrap class files
[javac] -extdirs Override location of installed extensions
[javac] -d Specify where to place generated class files
[javac] -encoding Specify character encoding used by source files
[javac] -source Provide source compatibility with specified release
[javac] -target Generate class files for specific VM version
[javac] -help Print a synopsis of standard options
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130)
at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:293)
at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:353)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370)
....>>
In catalina.out
<<19.07.2003 07:52:43 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8443
Compile failed; see the compiler error output for details.
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:842)
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:682)
at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:317)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370)
...>>
I solved it by re-installing tomcat in a directory that has no spaces in its
path. I don't know how I fell into this problem, because before, I ran tomcat
dozens of times successfully even with the space in the "..cat 4.1".
Suggestions:
For the exception case, have org.apache.jasper.compiler.Compiler.compile or
org.apache.tools.ant.taskdefs.Javac.compile with which arguments they call javac
and where they get them from!
One more strange observation:
- even though I installed with windows installer, the windows registry is
unchanged (still has the old paths with spaces e.g. in "JVM Option Number 0" or
"System.err File")
- it even has as "JVM library" a jdk1.3... that I deleted months ago
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org