Community
Participate
Working Groups
Build: I-20041109-1436 When you start Eclipse, you get several instances of the error pasted below in the log in your host instance. At first, I did not even notice it, as things appeared normal. Then I launched a runtime app and noticed that none of the plugins in my workspace are getting picked up. I then looked at the log of the runtime app, and I saw similar parse errors spit out by Update. I looked at the platform.xml that PDE generates for update, and I saw a default one (i.e. one with just features), which means that Update choked on the platform.xml PDE generated using Update's API. This makes the build unusable as self-hosting is impossible. !ENTRY org.eclipse.update.configurator 2004-11-10 02:27:55.575 !MESSAGE ConfigurationParser.parse() error: !STACK 0 org.xml.sax.SAXParseException: XML declaration may only begin entities. at org.apache.crimson.parser.Parser2.fatal(Unknown Source) at org.apache.crimson.parser.Parser2.fatal(Unknown Source) at org.apache.crimson.parser.Parser2.maybePI(Unknown Source) at org.apache.crimson.parser.Parser2.maybeMisc(Unknown Source) at org.apache.crimson.parser.Parser2.parseInternal(Unknown Source) at org.apache.crimson.parser.Parser2.parse(Unknown Source) at org.apache.crimson.parser.XMLReaderImpl.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.eclipse.update.internal.configurator.ConfigurationParser.parse (ConfigurationParser.java:69) at org.eclipse.update.internal.configurator.PlatformConfiguration.loadConfig (PlatformConfiguration.java:1007) at org.eclipse.update.internal.configurator.PlatformConfiguration.initializeCurren t(PlatformConfiguration.java:677) at org.eclipse.update.internal.configurator.PlatformConfiguration.<init> (PlatformConfiguration.java:88) at org.eclipse.update.internal.configurator.PlatformConfiguration.startup (PlatformConfiguration.java:631) at org.eclipse.update.internal.configurator.ConfigurationActivator.getPlatformConf iguration(ConfigurationActivator.java:323) at org.eclipse.update.internal.configurator.ConfigurationActivator.initialize (ConfigurationActivator.java:108) at org.eclipse.update.internal.configurator.ConfigurationActivator.start (ConfigurationActivator.java:71) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run (BundleContextImpl.java:958) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator (BundleContextImpl.java:954) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start (BundleContextImpl.java:937) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker (BundleHost.java:421) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume (AbstractBundle.java:366) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle (Framework.java:999) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles (StartLevelManager.java:577) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL (StartLevelManager.java:488) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel (StartLevelManager.java:273) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent (StartLevelManager.java:444) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent (EventManager.java:186) at org.eclipse.osgi.framework.eventmgr.EventThread.run (EventThread.java:104)
I have recently released a patch for cdcFoundation that serializes platform.xml "manually", as opposed to using the standard Transformer class from the J2SE. Perhaps this is causing the problem you describe.
From what I've seen the date info that you are persisting is written on the first line whereas it should be after the xml tag.
I notice a problem when a comment was inserted at the beginning of the xml file before the <?xml tag. This leads to errors. I was not able to start the jdt/ui AutomatedSuite. I used I200411091426.
re comment 1: was this critical so that it had to go into the rebuild (0800 worked)?
For the time being I removed the comment written at the top of the file and regular self hosting works fine now.
The cdc/foundation stuff is not critical for the eclipse sdk. The team providing the patch wanted to use it, and I also wanted to have it in a build earlier, to spot any issue (we just had a big one :( For reference, bug 77761 is the one I am talking about.
>and I also wanted to have it in a build earlier That's what nightly builds are for ;-)
Yes, the code was realeased on Friday, but I only now realized there were no nightly builds happening over the weekend, so I had assumed there were no issues. I've been using this code on an hourly basis, but my workspace is setup for feature based self hosting, and this problem did not occur.
It did not occur, of course, because when you're in feature-based self-hosting mode, PDE does not generate a platform.xml for Update.
