Community
Participate
Working Groups
Created attachment 264410 [details] Fixed feature file I am receiving an error message when exporting a product from my Eclipse Neon. The message in the "Error Log" view is: Problems parsing the feature file:C:/work_area/eclipse_neon32/features/org.eclipse.epp.package.committers.feature_4.6.0.20160613-1800/feature.xml The LOG has the following entry: !ENTRY org.eclipse.pde.build 4 17 2016-09-13 18:08:59.516 !MESSAGE Could not create feature: file:C:/work_area/eclipse_neon32/features/org.eclipse.epp.package.committers.feature_4.6.0.20160613-1800/feature.xml. !STACK 1 org.eclipse.core.runtime.CoreException: Problems parsing the feature file:C:/work_area/eclipse_neon32/features/org.eclipse.epp.package.committers.feature_4.6.0.20160613-1800/feature.xml. at org.eclipse.pde.internal.build.site.BuildTimeFeatureFactory.parseBuildFeature(BuildTimeFeatureFactory.java:85) at org.eclipse.pde.internal.build.site.BuildTimeFeatureFactory.createFeature(BuildTimeFeatureFactory.java:50) at org.eclipse.pde.internal.build.site.BuildTimeSite.createFeature(BuildTimeSite.java:458) at org.eclipse.pde.internal.build.site.compatibility.FeatureReference.getFeature(FeatureReference.java:39) at org.eclipse.pde.internal.build.site.BuildTimeSite.resolveFeatureReferences(BuildTimeSite.java:316) at org.eclipse.pde.internal.build.site.BuildTimeSite.findFeature(BuildTimeSite.java:285) at org.eclipse.pde.internal.build.site.BuildTimeSite.findFeature(BuildTimeSite.java:277) at org.eclipse.pde.internal.build.BuildScriptGenerator.generateFeatures(BuildScriptGenerator.java:249) at org.eclipse.pde.internal.build.BuildScriptGenerator.generate(BuildScriptGenerator.java:127) at org.eclipse.pde.internal.core.exports.FeatureExportOperation.doExport(FeatureExportOperation.java:255) at org.eclipse.pde.internal.core.exports.ProductExportOperation.run(ProductExportOperation.java:105) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Contains: Error parsing feature: "require" must include at least one "import" element. !SUBENTRY 1 org.eclipse.equinox.p2.publisher.eclipse 4 17 2016-09-13 18:08:59.516 !MESSAGE Problems parsing the feature file:C:/work_area/eclipse_neon32/features/org.eclipse.epp.package.committers.feature_4.6.0.20160613-1800/feature.xml. !SUBENTRY 2 org.eclipse.equinox.p2.publisher.eclipse 4 17 2016-09-13 18:08:59.516 !MESSAGE Error parsing feature: "require" must include at least one "import" element. Opening org.eclipse.epp.package.committers.feature_4.6.0.20160613-1800/feature.xml in the editor shows this: <requires> <!-- All requirements to features and the content of the product are defined in the product configuration epp.product since Eclipse Neon. For further details see the following bug: Bug 332989 - Allow parts of a package to upgraded or removed https://bugs.eclipse.org/bugs/show_bug.cgi?id=332989 --> </requires> The block <requires> </requires> is indeed empty after the fix of "Bug 332989". Moving the comments around the <requires> </requires> statements resolved the problem for me.
Markus, does the EPP builder rely on an empty requires section or can the solution outlined here be applied?
Just guessing, but yes, Tycho will probably work without the empty element in the XML file, I don't see a reason why it shouldn't. On the other hand I never tested the old PDE export with the EPP products, and my advice would be not to use that at all... the Tycho build is reliable and well tested.
Ok, closing it as won't fix then.
Actually, I have a better idea. I'll move it over to PDE to discuss if they would like to support it.
PDE team, this one is for you to discuss if you'd like to support exporting packages from PDE.
Actually, EPP feature is not part of my product. I only export pure CDT product with its dependency features. The export wizard process seems to parse all existing features anyway and reports an error above.
I think that the issue is that empty <requires></requires> block in feature.xml is not allowed by PDE. Therefore, all features must obey to that requirement. Other similar bugs are: bug 326207, bug 387616.
See comment #2. Basically we'd like to avoid changing any feature.xml. Instead, PDE Build should be enhanced to support features with an empty requires section.
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. Please reopen, if you plan to provide a fix.
