mb,
Furthermore deployment now goes wrong: the .ear file for my application does not contain any .jar or .war files.
You’re right, it appears that packaged deployment of EARs was broken by a seemingly unrelated change late in the QA cycle. This will be seen as a blocker internally so I’m sure at least a quick fix will be issued very soon. At the present time, the workaround is to use exploded deployment instead.
“The current configuration contains errors and this operation can have unpredictable results. Do you want to continue?”
I replicated that too, but it says the same thing when you click on Eclipse SDK and request an update check also. I then expanded the MyEclipse entry and selected each feature, and selected show properties and each one reports it is configured properly, as do all the Eclipse features. However, this does not occur on a plain Eclipse 3.0 install so I entered a bug report on it also. It does not seem to affect functionality, but we do need to make it stop warning, as you indicated. Thanks for pointing it out.