Summary: | Exception raised with loading or saving jsp files within web applications in Netbeans 5.5 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tom Dexter <digitalaudiorock> |
Component: | [OLD] Development | Assignee: | Java team <java> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tom Dexter
2007-01-28 16:29:28 UTC
Could you please specify what version of netbeans ebuild do you use? I tried the steps with netbeans-5.5-r3 and no exception occured. I'm running netbeans on Sun JDK 1.6.0. Maybe some dep of netbeans was built using higher version of JDK than the JDK you use for running the jsp file. You're absolutely correct. I've been using 1.5 as my user vm, in part because that's what I'm using as a system vm and the vm used by my system tomcat. If I switch my user vm to 1.6 I don't get the error either. Is there some reason that portions of netbeans would get compiled with 1.6 even though I'm not using it as a default? Oh...forgot to mention...I'm also usiing netbeans-5.5-r3. fordfrog@aceon /usr/share/netbeans-5.5 $ class-version-verify.py -t 1.5 -r . Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/apache/jasper/compiler/CompilerHacks$HackPageInfo.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/apache/jasper/compiler/CompilerHacks.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/apache/jasper/compiler/ExtractPageData.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/apache/jasper/compiler/GetParseData$BeanDataImpl.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/apache/jasper/compiler/GetParseData$PageInfoImpl.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/apache/jasper/compiler/GetParseData$TagInfoCacheRecord.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/apache/jasper/compiler/GetParseData.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/apache/jasper/compiler/NbValidator.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/apache/jasper/compiler/NodeConverterVisitor.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/apache/jasper/compiler/ParserControllerProxy.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/netbeans/modules/web/jspparser_ext/OptionsImpl.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/netbeans/modules/web/jspparser_ext/WebAppParseSupport$1.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/netbeans/modules/web/jspparser_ext/WebAppParseSupport$2.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/netbeans/modules/web/jspparser_ext/WebAppParseSupport$3.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/netbeans/modules/web/jspparser_ext/WebAppParseSupport$InitTldLocationCacheThread.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/netbeans/modules/web/jspparser_ext/WebAppParseSupport$JasperSystemClassLoader.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/netbeans/modules/web/jspparser_ext/WebAppParseSupport$ParserClassLoader.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/netbeans/modules/web/jspparser_ext/WebAppParseSupport$RRef.class Bad: 1.6 ./enterprise3/modules/ext/jsp-parser-ext.jar org/netbeans/modules/web/jspparser_ext/WebAppParseSupport.class CVV: 5 Checked: 25293 Good: 25274 Bad: 19 It revealed that single jar was built with target 1.6 which caused the bug so I turned back on rewrite of build.xml files which solved that. New ebuild is committed in CVS. It'll take few hours till it hits the mirrors. Thank you for reporting the bug. Thanks! |