Eclipse Community Forums: Java Development Tools (JDT) » Annoying stack trace when closing a project

Home » Language IDEs » Java Development Tools (JDT) » Annoying stack trace when closing a project(Annoying stack trace when closing a project)

Show: Today's Messages :: Show Polls :: Message Navigator

Annoying stack trace when closing a project [message #1833167]

Mon, 05 October 2020 10:24

Eitan Rosenberg

Messages: 139
Registered: October 2018

Senior Member

After installing eclipse-java-2020-09 when I close a project I get this stack trace:

For example:

!ENTRY org.eclipse.m2e.logback.appender 4 0 2020-10-04 08:29:28.711
!MESSAGE Launch configuration MyMaven references closed project MyMaven
!STACK 1
org.eclipse.core.runtime.CoreException: Launch configuration MyMaven references closed project MyMaven
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:224)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.debug.internal.core.LaunchManager$ConfigurationNotifier.notify(LaunchManager.java:208)
at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.setDirty(LaunchConfigurationWorkingCopy.java:521)
at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.setAttribute(LaunchConfigurationWorkingCopy.java:409)
at org.eclipse.m2e.jdt.internal.launch.MavenRuntimeClasspathProvider.disable(MavenRuntimeClasspathProvider.java:401)
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 2020-10-04 08:29:28.711
!MESSAGE Launch configuration MyMaven references closed project MyMaven

My environment:
- Eclipse installation is done using eclipse-java-2020-09-R-win32-x86_64.zip .
- Java installation is done using openjdk-15_windows-x64_bin.zip
- The workspace is fresh.
- Windows 10

Report message to a moderator