There are two ways to import MAT source into Eclipse:
1. Import } General } Existing Projects into Workspace
2. Import } Maven } Existing Maven Projects
The former works because we check in Eclipse .project, .classpath, and .settings files/directories into the source tree.
Using either method with a fresh Eclipse 2024-12 for Eclipse Committers IDE causes hundreds of exceptions of the form:
Access restriction: The [...] is not API (restriction on required library '[...]/org.hamcrest_3.0.0.jar')
This can be resolved by going into workspace or project preferences and changing "Forbidden reference (access rules)" to "Warning" under Java Compiler } Errors/Warnings
From my understanding, it's generally no longer recommended to check in Eclipse .project/.classpath/.settings files/folders into the source tree and instead to import using Existing Maven Projects and let the M2Eclipse plugin handle the
Eclipse projects/settings; however, I can't find any way to tell M2Eclipse in pom.xml files to automatically set "Forbidden reference" to "Warning".
So it seems to me there are two options:
A. Change the "Forbidden reference" setting in the checked-in Eclipse settings and discourage using Import } Existing Maven Projects in the Contributor Reference, or
B. Remove all checked-in Eclipse settings from the source tree, discourage using Import } Existing Projects into Workspace in the Contributor Reference, and add a step in the Contributor Reference to change the "Forbidden reference" setting.
Any preferences? I lean towards A out of inertia.
Kevin Grigorenko
Application Runtimes SWAT, IBM Software Support