eclipse-platform
Project explorer - Hierarchical Presentation - close parent doesn't close child projects
Currently when the hierarchical presentation is enabled in the project explorer and a root project is closed its child projects still remain open. The only solution is to close each child project manually. This is especially bad when using Gradle/Buildship where a build is usually partitioned into multiple interdependent subprojects. In this case the current behavior of closing only the root project will often lead to compile errors in the remaining sub projects since dependencies are no longer available.
This issue has previously been reported on Bugzilla, but was never fixed.
@Zuplyx Thanks, we also need this so badly...
@jukzi This is nothing personal and you have been chosen randomly but it fits here: Your statement is the perfect example why Eclipse as an IDE is losing more and more ground to intellij/vs code. Rather simple but important features for a broad range of users are not addressed for years.
We as a company love Eclipse (and yes, we do submit PRs) and we would love to spend money directly to the Eclipse / JDT project for paying the developers to improve the product on short-term - but the only thing we can do is to donate money to the Eclipse foundation.
It is sad to see that the reflective Eclipsecon 2022 talk "What Eclipse IDE must learn from other IDEs to survive?" still holds up 100%... https://www.youtube.com/watch?v=jyIYPz67KKA
@patric-r It's a bit unrelated to the issue bug if you are interested in funding Eclipse IDE development there is one more option to join https://www.eclipse.org/org/workinggroups/eclipse-ide-charter.php and participate in the decisions how priorities are set and what is funded. There are also people offering contract work and I can get you in touch if interested. We have also tried to get more direct funding being discoverable but so far there is no interest from EF (https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/965), please raise your voice in support.
Correct funding discussion link is https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/963 .
we would love to spend money directly to the Eclipse
Then please join or fund the IDE Working Group, we desperately need more.
Your statement is the perfect example why Eclipse as an IDE is losing more and more ground to intellij/vs code.
I asked the same on the EclipseCon Talk, so why you (or everyone) are not using intellij/vs code then?
Beside that as Jörg mentioned you can try to give money to Eclipse in general, but if you want a specific issue fixed it is most often better to pay someone directly, from your statement it is not clear if you cant do that (for whatever reason) or don't know how to do that, in the later case you can for example ask on the https://accounts.eclipse.org/mailing-list/platform-dev for someone that is open for hire, for example I already did fixed specific bugs for some companies in the past, maybe there are more people for hire as well.
