Support launching with features and plugins selected

[jonahgraham]

Tested on SDK-I20250207-1800. This is not a regression, I don't think this ever worked.

1. Create a plugin + test fragment

• example zip - but you can just run the following wizards for the same effect, new Plug-in project, new Fragment, new JUnit test

2. Create a JUnit Plug-in test launch configuration

• e.g. right-click on the test created in 1 and choose Run As -> JUnit Plug-in test

3. Open the launch configuration
4. In plug-ins tab, choose Launch with: Features selected below
5. Press Select Plug-ins

Expected: The test fragment created in 1 is available to select
Actual: Only plugins are available

The fallback/workaround is to use Launch with Plug-ins selected below which does allow the fragment to be selected, but other configuration is trickier.

Screenshots:

"Launch with: Features selected below" missing mytestfragment

Stack trace:

If I try to run the launch configuration I get the following exception because mytestbundle isn't included (this is expected since we couldn't add it above):

Class not found mytestfragment.MyTest
java.lang.ClassNotFoundException: mytestfragment.MyTest cannot be found by mybundle_1.0.0.qualifier
	at org.eclipse.osgi.internal.loader.BundleLoader.generateException(BundleLoader.java:567)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass0(BundleLoader.java:562)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:438)
	at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:195)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526)
	at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:652)
	at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner$BundleClassLoader.findClass(RemotePluginTestRunner.java:52)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:593)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.loadClass(RemoteTestRunner.java:758)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.loadClasses(RemoteTestRunner.java:481)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:504)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:748)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:443)
	at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:83)
	at org.eclipse.pde.internal.junit.runtime.PlatformUITestHarness.lambda$0(PlatformUITestHarness.java:45)

[laeubi]

Create a plugin + test fragment

I can just always emphasize that there is no such thing as "test fragment" neither in PDE nor OSGi, so this is just a usual fragment.

"Launch with: Features selected below" missing mytestfragment

You need to include the fragment in the feature if you want to launch with features.

The fallback/workaround is to use Launch with Plug-ins selected below which does allow the fragment to be selected, but other configuration is trickier

I think one actually wants something else here that is similar to what we offer for products and such an option would read:

Launch with Plug-ins and Features selected below

[jonahgraham]

I think one actually wants something else here that is similar to what we offer for products and such an option would read:

Launch with Plug-ins and Features selected below

Yes, I think this is what is needed.

"Launch with: Features selected below" missing mytestfragment

You need to include the fragment in the feature if you want to launch with features.

I think this is a good workaround until the above is fixed.

[laeubi]

I changed the title because I also found this sometimes missing (not only for fragments).