|Re: Need workaround for XML parser error [message #4794 is a reply to message #4724]
||Wed, 02 February 2005 16:23
| Paul Slauenwhite
Registered: July 2009
After further inspection, the plugin.xml files for the
org.apache.jakarta_commons_logging_1.0.3 plug-ins were created using an
external textual editor (Microsoft tool) and not the Eclipse plugin.xml
editor. As such, the Byte Order Mark (BOM) was incorrect (EF BB BF) and the
Crimson XML parser that is shipped with the Sun JDK 1.4.2 did not handle
I will reopen https://bugs.eclipse.org/bugs/show_bug.cgi?id=82305 and
fix the problem accordingly.
"Merlin Vincent" <firstname.lastname@example.org> wrote in message
> Hello -
> I am running into the same problem reported in Hyades bug 82305. That is,
> the byte order mark in the log4j plugin.xml causes a parser error. I
> sympathize with the position that this is really an eclipse issue, but I
> need to get this tool running if at all possible. Can you help me, please?
> I have edited the log4j plugin.xml file to remove the BOM, as the bug
> report suggests, and I no longer get the "can't parse this file" error.
> But eclipse still encounters errors, and won't offer the profiling
> The PDE Runtime Plugin Registry view doesn't show any of the Hyades
> plugins, while the PDE Plugins view shows about 32 of them. The PDE error
> log contains a long list of "Missing required plugin..." for various
> Hyades plugins.
> What can I do to get this working?
Powered by FUDForum
. Page generated in 0.01897 seconds