What is the best way to track m2e issues that affect the vscode-java project?

[tomjenkinson]

Hi, when trying to a particular Maven project (https://github.com/jakartaee/platform-tck) into VSCode with the Java support enabled, the project is giving me a lot of problems with reading the project.

Eventually I have landed at eclipse-m2e/m2e-core#1912 which does seem possibly likely to be the cause (e.g. parts like https://github.com/jakartaee/platform-tck/blob/main/tcks/apis/cdi-ee-tck/tck/pom.xml#L390-L396) and when I look in the "Language Support for Java" output in the OUTPUT tab of VSCode I see (where <ROOT_OF_PLACE_CHECKED_OUT_TO> is a real fully qualified path on my machine I have removed for sharing more publicly here):
Cannot create a link to '<ROOT_OF_PLACE_CHECKED_OUT_TO>/platform-tck' because it overlaps the location of the project that contains the linked resource. org.eclipse.core.internal.resources.ResourceException: Cannot create a link to ''<ROOT_OF_PLACE_CHECKED_OUT_TO>/platform-tck' because it overlaps the location of the project that contains the linked resource. at org.eclipse.core.internal.resources.Resource.assertLinkRequirements(Resource.java:204) at org.eclipse.core.internal.resources.Resource.createLink(Resource.java:671) at org.eclipse.m2e.jdt.internal.AbstractJavaProjectConfigurator.getFolder(AbstractJavaProjectConfigurator.java:907) at org.eclipse.m2e.jdt.internal.AbstractJavaProjectConfigurator.addResourceDirs(AbstractJavaProjectConfigurator.java:543) at org.eclipse.m2e.jdt.internal.AbstractJavaProjectConfigurator.addProjectSourceFolders(AbstractJavaProjectConfigurator.java:397) at org.eclipse.m2e.jdt.internal.AbstractJavaProjectConfigurator.configure(AbstractJavaProjectConfigurator.java:165) at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:127) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.lambda$6(ProjectConfigurationManager.java:506) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:458) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:339) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:500) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:279) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.lambda$1(ProjectConfigurationManager.java:166) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:458) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:339) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:278) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:139) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:130) at org.eclipse.jdt.ls.core.internal.managers.MavenProjectImporter.importToWorkspace(MavenProjectImporter.java:242) at org.eclipse.jdt.ls.core.internal.managers.ProjectsManager.importProjects(ProjectsManager.java:164) at org.eclipse.jdt.ls.core.internal.managers.ProjectsManager.initializeProjects(ProjectsManager.java:126) at org.eclipse.jdt.ls.core.internal.handlers.InitHandler$1.runInWorkspace(InitHandler.java:263) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:43) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

My main question is, is it described that I as a user of VSCode should create a tracking issue in https://github.com/redhat-developer/vscode-java for what looks like relevant issues or should I as a user of VSCode understand that it uses m2e and primarily track it the relevant components repo?

Thanks for any guidance that can be offered