Community
Participate
Working Groups
We should continuously abandon "Require-Bundle" notation. PDE should rely on the currently loaded workspace projects to look for Extension Point schema and not in the bundles specified by "Require-Bundle" as it currently does. I am only using "Import-Bundle" throughout my projects. Creating and using extensions is still possible though. So it seems that the warning the Manifest Editor is printing out about missing schema files relies on the "Require-Bundle" while the editor itself can perfectly work without "RB".
I know :) I believe we have one or two bugs about this issue, can't find them atm. Do you want to create a patch for this issue ;)?
btw, where is the warning coming up? Can you give me your workflow?
It came up when I opened a plugin.xml file. But I cannot reproduce it now. I wanted to attach a screenshot. Anyway, I think I am not that deep into PDE yet, to provide a patch for this, unfortunately. However, maybe you could point me into a direction. I think the messagebox that asks you to add the schema-containing plugin to the required-bundles should go away too, and might be a good point to look at for starters like me :)
Similar issue is seen with IBM JAVA while executing Automated Test Suite of pdeapitooling, Error: ECL (eclipse) recordError type=TestError org.eclipse.pde.api.tools.model.tests.ApiDescriptionTests testBinaryHasApiDescription Check the property : -DrequiredBundles=... ECL Missing required bundle(s): org.eclipse.core.runtime, ECL (eclipse) org.eclipse.core.runtime.CoreException: Check the property : -DrequiredBundles=... ECL Missing required bundle(s): org.eclipse.core.runtime, ECL at org.eclipse.pde.api.tools.model.tests.TestSuiteHelper.addAllRequired(TestSuiteHelper.java:503) ECL at org.eclipse.pde.api.tools.model.tests.TestSuiteHelper.createTestingBaseline(TestSuiteHelper.java:366) ECL at org.eclipse.pde.api.tools.model.tests.TestSuiteHelper.createTestingBaseline(TestSuiteHelper.java:128) ECL at org.eclipse.pde.api.tools.model.tests.ApiDescriptionTests.testBinaryHasApiDescription(ApiDescriptionTests.java:820) ECL at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:692) ECL at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:319) ECL at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:36) ECL at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:32) ECL at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587) ECL at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198) ECL at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) ECL at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) ECL at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) ECL at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) ECL at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) ECL at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) ECL at org.eclipse.equinox.launcher.Main.run(Main.java:1515) ECL at org.eclipse.equinox.launcher.Main.main(Main.java:1488) ECL at org.eclipse.core.launcher.Main.main(Main.java:34) ECL Failing tests: 19 RTR 1) org.eclipse.pde.api.tools.model.tests.ApiDescriptionTests testBinaryHasApiDescription RTR 2) org.eclipse.pde.api.tools.model.tests.ApiDescriptionTests testBinaryHasNoApiDescription RTR 3) org.eclipse.pde.api.tools.model.tests.ApiBaselineTests testUsesDirective RTR 4) org.eclipse.pde.api.tools.model.tests.ApiBaselineTests testXInternalDirective RTR 5) org.eclipse.pde.api.tools.model.tests.ApiBaselineTests testGetLocation RTR 6) org.eclipse.pde.api.tools.model.tests.ApiBaselineTests testNestedJarComponent RTR 7) org.eclipse.pde.api.tools.model.tests.ApiBaselineTests testFindJavaLangObject RTR 8) org.eclipse.pde.api.tools.model.tests.ApiBaselineTests testDependents RTR 9) org.eclipse.pde.api.tools.model.tests.ApiBaselineTests testResolvePackage RTR 10) org.eclipse.pde.api.tools.model.tests.ApiBaselineTests testPrerequisites RTR 11) org.eclipse.pde.api.tools.model.tests.ApiBaselineTests testResolveJavaLangPackage RTR 12) org.eclipse.pde.api.tools.model.tests.ApiBaselineTests testXFriendsDirective RTR 13) org.eclipse.pde.api.tools.model.tests.ApiBaselineTests testResolvePackageWithinComponent RTR 14) org.eclipse.pde.api.tools.model.tests.ApiBaselineTests testResolveSystemPackage RTR 15) org.eclipse.pde.api.tools.model.tests.ApiBaselineTests testNotExported RTR 16) org.eclipse.pde.api.tools.reference.tests.SearchScopeTests testVisitEntireComponentsScope RTR 17) org.eclipse.pde.api.tools.reference.tests.SearchScopeTests testVisitSpecificTypes RTR 18) org.eclipse.pde.api.tools.reference.tests.SearchScopeTests testVisitTypeScope RTR 19) org.eclipse.pde.api.tools.builder.tests.OSGiLessAnalysisTests testAnalyzer IBM Java Version: Java(TM) SE Runtime Environment (build pxi3270_27sr5-20180612_01(SR5)) IBM J9 VM (build 2.7, JRE 1.7.0 Linux x86-32 20180611_389116 (JIT enabled, AOT enabled) J9VM - R27_jvm.27_20180611_1242_B389116 JIT - tr.r13.java_20180611_389116 GC - R27_jvm.27_20180611_1242_B389116 J9CL - 20180611_389116) JCL - 20180605_01 based on Oracle jdk7u181-b09
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
