|
From: dAniel h. <ge...@th...> - 2007-07-03 00:42:29
|
Hello, yesterday I've noticed a NPE when I've tried to use sidekick-complete in a CSS file. I've debugged this using Eclipse and found that cssproperties was null, although it should have been set in during initialization. Somehow cssSideKickCompletion.readCompletionConfig did not finish, nor threw an error. At some point there was a java.lang.NoSuchMethodError in org.apache.xerces.util.XMLCatalogResolver.init. The activity log showed only [debug] CssSideKickCompletion: Parsing configuration file: jeditresource:/XML.jar!/xml/completion/css-complete.xml but missed [debug] CssSideKickCompletion: Parsing done, found 95 css properties and 9 css units or any error. I could not really debug this using Eclipse either (and am no Java expert for sure), but the solution then was to remove ~/.jedit/jars/xml-commons-resolver.jar! I don't know where the file is from, maybe I had copied it there manually while trying to build the XML plugin some years ago - I'm not sure at all. The file is dated 2004-06-27 and the manifest says 1.2.2 (Sun Microsystems Inc.). Just in case this is an old library of some plugin, we should make sure that it gets removed. Is there any way to detect such library messups (and report it to the user somehow)? At least it seems like there was no indication in the activity log (apart from the NPE when calling sidekick-complete). |