Inconsistent add -ea to JUnit functionality

Version: 2025-12 (4.38)
Build id: I20251201-0920

https://bugs.eclipse.org/bugs/show_bug.cgi?id=45408 added the "Add -ea to new JUnit launches" defaulting to add, but avoiding corruption of existing launches; good.

I have recently been forced to run many JUnit Plugin tests rather than my usual JUnit tests and find my assertions are ignored; bad.

It seems -ea is not added to JUnit Plugin test launches. Surely it should be, either in accordance with the existing preference or a new preference?

Retrofitting -ea to casual Run As ... launches is painful since launch names are not always clear.

Start by tracing how JUnit Plugin test launches are created and how the existing “Add -ea to new JUnit launches” preference is applied. Compare those launches with ordinary JUnit launches and the behavior described in bug 45408; done means the preference consistently controls assertion flags for new JUnit Plugin test launches, with coverage for the affected launch type.

Written by the indexing model from the issue text.