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 2002/02/14 15:27:19 UTC
DO NOT REPLY [Bug 6464] New: -
jspc generates bad package names on Windows NT
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=6464>.
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=6464
jspc generates bad package names on Windows NT
Summary: jspc generates bad package names on Windows NT
Product: Tomcat 4
Version: 4.0.2 Final
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Major
Priority: Other
Component: Jasper
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: philippe-rostaing@sab2i.com
How to reproduce :
------------------
Find a computer running Windows NT.
Directory structure : x\en\demo.jsp
cd x
jspc -uriroot . -d . en/demo.jsp
file generated : x\demo.java
package name in source : none
jspc -p en en/demo.jsp
file generated : x\demo.java
package name in source : package en.;
Both commands should have generated x\en\demo.java, with a package name of "en".
More info :
-----------
The reason seems to be the incorrect use of '/' as a path separator in
org.apache.jasper.CommandLineContext.getServletPackageName()
Replacing '/' with '\\' solved the proble on NT. But then, it would not work on
Unix.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>