Bug 539935 - Removing hierarchical Maven project makes Eclipse unresponsive "performing changes"
Summary: Removing hierarchical Maven project makes Eclipse unresponsive "performing ch...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.9   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2018-10-08 17:21 EDT by Garret Wilson CLA
Modified: 2020-09-28 17:12 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Garret Wilson CLA 2018-10-08 17:21:17 EDT
I'm using Eclipse 2018-09 on Windows 10 I had an imported Maven project with several modules that had an aggregate POM as the parent. In Project Explorer I switched to a hierarchical view. Then I tried to remove the parent project. Eclipse says "Performing changes..." in the dialog, and at the bottom it says "Reporting encoding changes.: (0%)".

And then Eclipse becomes unresponsive. Clicking the little red "cancel" icon does nothing except make the cancel icon become gray. I had no option but to kill the Eclipse process.

When I reloaded Eclipse, I got an error:

> 'Refreshing workspace' has encountered a problem.
> Problems occurred while refreshing local changes.

It tells me that:

> The project description file (.project) for [the project I removed, which still
> shows up] is missing.  This file contains important information about the
> project.  The project will not function properly until this file is restored.

Project Explorer still shows the project in the tree, although it no longer shows as hierarchical. (Apparently it deleted the parent `.project`, but still shows the child projects. So I selected the related projects (which used to be hierarchical), and remove them, this time successfully.

I re-imported the project, and then removed them, successfully.
Comment 1 Andrey Loskutov CLA 2018-10-08 17:29:21 EDT
If it is reproducible, please create jstack dump *before* killing Eclipse and attach the dump here.
Comment 2 Eclipse Genie CLA 2020-09-28 17:12:42 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.