Closed laeubi closed 2 months ago
As a workaround I edited the classpath settings directly in the filesystem
so I can use the project again.
These are the bundles that show up in my install
JUnit 5 is also party wrecked now as it pulls in an almost empty hamcrest-core leading to compile errors:
As a workaround I edited the classpath settings directly in the filesystem
I get the same error but even for a JUnit-4 container:
Invalid classpath container: 'JUnit 4' in project 'org.eclipse.xtext.xbase.lib.tests'
Using a Eclipse IDE for Eclipse Committers
Version: 2024-09 M3 (4.33.0 M3)
Build id: 20240822-1019
I get the same error but even for a JUnit-4 container:
As mentioned the JUnit 4
breaks completely, JUnit 5
breaks if you use any Hamcrest class, the while Eclipse SDK workspace is now broken as well because of org.eclipse.osgi
what is a dependency of almost everything:
Moved to JDT/UI, where the junit containers are implemented.
As suggested by @laeubi I verified that this can be fixed by widening the version range in BuildPathSupport.HAMCREST_PLUGIN
and BuildPathSupport.HAMCREST_CORE_PLUGIN
.
According to the release notes it looks like https://github.com/hamcrest/JavaHamcrest/releases/tag/v3.0 only changed the class-file version corresponding to Java-1.8, so it should be a drop-in replacement since JDT only support Java-1.8 now (luckily).
Adapting the version range seems therefore sufficient.
see the same https://github.com/eclipse/xtext/issues/3178
i get similar: "Invalid classpath container: 'JUnit 4' in project 'org.eclipse.osgi"
I updated my IDE (from
Eclipse for RCP and RAP Developers 4.33.0.20240711-1200
>Eclipse for RCP and RAP Developers 4.33.0.20240822-0820
) as nowand now one of my projects is wrecked with
I can't even expand the project anymore because it results in
The project also has an error marker: