Community
Participate
Working Groups
From DJ Houghton (bug 28637) I got this error message ("[Fatal Error] :1:1: Content is not allowed in prolog.") in my console with build i0618-1804. - started Eclipse on a clean workspace. - switched to the CVS perspective - started checking out projects - turned off auto-build - changed default text font along with some other prefs - changed SWT classpath file to be the win32 one - hit Ctrl-B to build - waited Noticed the error message in my console. No other side effects. Here is a list of projects in my workspace: org.eclipse.help.ui.win32 org.eclipse.update platform-launcher org.apache.lucene org.eclipse.compare org.eclipse.core.filebuffers org.eclipse.core.resources org.eclipse.core.runtime org.eclipse.core.runtime.compatibility org.eclipse.debug.core org.eclipse.debug.ui org.eclipse.help org.eclipse.help.appserver org.eclipse.help.base org.eclipse.help.ide org.eclipse.help.ui org.eclipse.help.webapp org.eclipse.jdt.core org.eclipse.jdt.debug org.eclipse.jdt.debug.ui org.eclipse.jdt.junit org.eclipse.jdt.junit.runtime org.eclipse.jdt.launching org.eclipse.jdt.ui org.eclipse.jface org.eclipse.jface.text org.eclipse.osgi org.eclipse.osgi.services org.eclipse.osgi.util org.eclipse.pde.build org.eclipse.pde.core org.eclipse.pde.runtime org.eclipse.pde.ui org.eclipse.search org.eclipse.swt org.eclipse.team.core org.eclipse.team.cvs.core org.eclipse.team.cvs.ssh org.eclipse.team.cvs.ui org.eclipse.team.ui org.eclipse.text org.eclipse.tomcat org.eclipse.ui org.eclipse.ui.editors org.eclipse.ui.ide org.eclipse.ui.views org.eclipse.ui.workbench org.eclipse.ui.workbench.texteditor org.eclipse.update.core org.eclipse.update.ui
I can not reproduce the problem. DJ - what is your JRE ?
java version "1.4.1" J9 - VM for the Java(TM) platform (build 2.1) IBM J9SE VM (build 2.1, J2RE 1.4.1 IBM J9 build 20040510 (JIT enabled))
I also get this error when doing a full build on this workspace.
Note I just got these messages again while doing a full build on a rather large workspace with a bunch of other plug-ins installed. I turned on builder debug information and it looks like it is inside an ExternalTools builder when the message is being printed out. VM version is: IBM J9SE VM (build 2.1, J2RE 1.4.2 IBM J9 build 20040610 (jit enabled)) I can provide (via email) the XML file which was being run. (javadoc generation I believe)
This error message only appears when using the IBM VM. It's coming from the XML parsing implementation included with the IBM JRE.
Is there something different that we should be doing with our XML so we don't get this error. The words "Fatal Error" sound bad. I presume that there are no adverse side effects?
DJ can you just provide the xml that comes before the declaration of the project in the buildfile? This is the interesting part.
DJ can you indicate which builder or provide the XML that is causing the problem.
Oops...sorry for the delay. The strange thing is that there wasn't anything before the <project> declaration in the file. (well, except for <?xml version="1.0" encoding="UTF-8"?>) I talked to the owner of the project and there were set-up steps that I had to do with that particular project. When looking at the steps, it included using the SUN JDK among other things....
When running on IBM VM (J9) and building my workspace I get lots of: [Fatal Error] :1:68: XML document structures must start and end within the same entity. [Fatal Error] :1:1: Content is not allowed in prolog.
Needs more investigation but I really doubt there is anything we can do...we do not provide the XML parser.
The question is whether we have fatal errors in our files or whether this is an IBM VM bug.
Some plugin that is parsing XML is not adding an error handler. See bug 18350. Now the trick is to find the guilty plugin...Ant adds more error handlers than I know what to do with :-)
The error handler allows other components to handle the error. Why would that component ignore a fatal error? Bug 18350 says that they sometimes parse invalid xml and hence it's OK to swallow error in such cases. This should not be the case when building my workspace that has no errors at all (PDE plugin.xml checking enabled). We should find out which files cause these errors.
Agree. A test case would be great.
It always happens to me when I rebuild org.eclipse.ant.core. But this can't be the only one since I have many entries in the console.
This problem surfaces as the BuilderUtil class is passing malformed XML to the debug launch configuration framework. I have made the required changes to the BuilderUtil class and have logged bug 73397 to cover all the other cases in debug land where this problem could crop up.
Reordered how the BuilderUtils deals with the config handle.
Please verify Jared.
DarinS, the way I read the code, we'll still get this output for projects created during the 3.0 cycle (up to RC1). Since we were told to support this case, we should probably further re-order the code to only do the parsing as the last attempt.
Same fix applied for 3.0 "interim format" builders. Please verify change to BuilderUtils, DarinS.
Verified.
