closed project tests still show up in the "run configurations" drop down

[dabraham02124]

Problem Statement

The "Run Configurations" drop down button shows "Run As TestNG test" options for projects that are closed. The dialog too. There's no steps to reproduce it, it's always there. It's an issue in that it hides the run configurations for projects that I'm working on now, so I have to open the dialog, then scroll a bunch (I have lots of tests).

Any relate message in "Error Log" view

"Windows -> Show View -> Others -> Error Log"

Oh yes. Tons. The way I read them, they're complaining about the fact that these are still visible, not telling me why they're still visible. It has a

1. "Message:"
   1. "Launch configuration {Test} references closed project {project}"
2. "Exception Stack Trace:"
   1. "An exception stack trace is not available."
3. "Message Data"

eclipse.buildId=4.18.0.I20201202-1800
java.version=15.0.1
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.jee.product -keyring /Users/{user}/.eclipse_keyring
Command-line arguments:  -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -keyring /Users/abrahamd/.eclipse_keyring

This is a continuation of log file /Users/{user}/eclipse-workspace-2019-06/.metadata/.bak_3.log
Created Time: 2021-03-10 22:06:04.319

If I look in that file I see lots of entries of this form:

!SESSION 2021-03-04 21:27:18.807 -----------------------------------------------
eclipse.buildId=4.18.0.I20201202-1800
java.version=15.0.1
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.jee.product -keyring /Users/{user}/.eclipse_keyring
Command-line arguments:  -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -keyring /Users/{user}/.eclipse_keyring

This is a continuation of log file /Users/{user}/eclipse-workspace-2019-06/.metadata/.bak_2.log
Created Time: 2021-03-09 22:44:04.214

!ENTRY org.eclipse.m2e.logback.appender 4 0 2021-03-09 22:44:04.214
!MESSAGE Launch configuration IntegrationTest.runSimpleQueryTest references closed project {project}
!STACK 1
org.eclipse.core.runtime.CoreException: Launch configuration IntegrationTest.runSimpleQueryTest references closed project {project}
        at org.eclipse.jdt.launching.JavaRuntime.abort(JavaRuntime.java:1843)
        at org.eclipse.jdt.launching.JavaRuntime.getJavaProject(JavaRuntime.java:1715)
        at org.eclipse.m2e.jdt.internal.launch.MavenLaunchConfigurationListener.updateLaunchConfiguration(MavenLaunchConfigurationListener.java:55)
        at org.eclipse.m2e.jdt.internal.launch.MavenLaunchConfigurationListener.launchConfigurationChanged(MavenLaunchConfigurationListener.java:40)
        at org.eclipse.debug.internal.core.LaunchManager$ConfigurationNotifier.run(LaunchManager.java:225)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
        at org.eclipse.debug.internal.core.LaunchManager$ConfigurationNotifier.notify(LaunchManager.java:209)
        at org.eclipse.debug.internal.core.LaunchManager.launchConfigurationChanged(LaunchManager.java:2132)
        at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.writeNewFile(LaunchConfigurationWorkingCopy.java:374)
        at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.doSave0(LaunchConfigurationWorkingCopy.java:257)
        at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.doSave(LaunchConfigurationWorkingCopy.java:227)
        at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.doSave(LaunchConfigurationWorkingCopy.java:185)
        at org.eclipse.m2e.jdt.internal.launch.MavenRuntimeClasspathProvider.disable(MavenRuntimeClasspathProvider.java:403)
        at org.eclipse.m2e.jdt.internal.launch.MavenRuntimeClasspathProvider.disable(MavenRuntimeClasspathProvider.java:427)
        at org.eclipse.m2e.jdt.internal.launch.MavenLaunchConfigurationListener.mavenProjectChanged(MavenLaunchConfigurationListener.java:72)
        at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:824)
        at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:990)
        at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob.lambda$0(ProjectRegistryRefreshJob.java:149)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:179)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:153)
        at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:101)
        at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1374)
        at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob.run(ProjectRegistryRefreshJob.java:84)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
!SUBENTRY 1 org.eclipse.jdt.launching 4 124 2021-03-09 22:44:04.214
!MESSAGE Launch configuration IntegrationTest.runSimpleQueryTest references closed project {project}

The Dependency Management tool for your project

• [✓] Maven
• Gradle
• Ant
• Eclipse Buildpath (aka. Use "TestNG Library" for your project in Eclipse)

Operating System

• Windows
• Linux
• [ ✓] OSX

plugin version

TestNG 7.3.0.202008060412 org.testng.eclipse.feature.group Cedric Beust

I haven't found anything by duckduckgoing, I don't see this in the list of open issues,... If I missed something, my apologies. If there's anything I can add to make this easier to work out, please let me know.

Thank you very much, both for a lovely tool, and for looking into this. Be well.