Debug Perspective Auto Closer

Add this URL to your Eclipse Installation to reach this solution's update site.

2020-03 (4.15), 2019-12 (4.14), 2019-09 (4.13), 2019-06 (4.12), 2019-03 (4.11), 2018-12 (4.10), 2018-09 (4.9), Photon (4.8), Oxygen (4.7), 2020-06 (4.16), 2020-09 (4.17), 2020-12 (4.18), 2021-03 (4.19)

https://gammawolf.github.io/DPAC-Publish
Learn more...
Solution Description

Automatically opens previous perspective when debugging ends.

Behaviors: (configurable: Preferences -> Debug Perspective Auto Closer)
1) [default] when all debug launches have terminated, changes to perspective active on first launch
2) when any debug launch has terminated, changes to perspective active on that launch

Remarks:
- Only changes perspective when in debug perspective.

Source:
https://github.com/GammaWolf/eclipse-debug-perspective-auto-closer-plug…

Contact:
slysamurai
yahoo
com

Categories: IDE

Additional Details

Eclipse Versions: 2020-03 (4.15), 2019-12 (4.14), 2019-09 (4.13), 2019-06 (4.12), 2019-03 (4.11), 2018-12 (4.10), 2018-09 (4.9), Photon (4.8), Oxygen (4.7), 2020-06 (4.16), 2020-09 (4.17), 2020-12 (4.18), 2021-03 (4.19)

Platform Support: Windows, Mac, Linux/GTK

Development Status: Alpha

Date Created: Friday, December 28, 2018 - 21:41

License: MIT

Date Updated: Friday, January 15, 2021 - 10:16

Submitted by: Francesco **********

Date Ranking Installs Clickthroughs
April 2024 377/658 14 4
March 2024 368/694 29 5
February 2024 396/687 19 2
January 2024 368/691 25 4
December 2023 382/671 22 8
November 2023 308/686 49 3
October 2023 329/673 39 8
September 2023 280/663 51 4
August 2023 381/673 20 4
July 2023 366/668 23 3
June 2023 333/669 33 1
May 2023 375/671 25 3
View Data for all Listings

Unsuccessful Installs

Unsuccessful Installs in the last 7 Days: 0

Download last 500 errors (CSV)

Marketplace Drag to Install Button

By adding the following code below to your website you will be able to add an install button for Debug Perspective Auto Closer .

HTML Code:

Markdown Syntax:

Output:

Drag to your running Eclipse* workspace. *Requires Eclipse Marketplace Client

Reviews Add new review

Submitted by Ivan B on Sun, 03/29/2020 - 12:32

Hi Francesco.

Thank you for your efforts.

 

I tried the plugin in 2019-12 and 2020-03 and it doesn't seem to work. Any clues?

In Error Log however I do see some activities related to plugin:

eclipse.buildId=4.14.0.I20191210-0610
java.version=13.0.1
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.jee.product
Command-line arguments:  -data file:/<full_path>/ -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product

1)
org.eclipseplugins.autoclosedebugperspective
OK
Sun Mar 29 19:22:27 EEST 2020
launched org.eclipse.debug.core.Launch@4e88ef1e

2)
org.eclipseplugins.autoclosedebugperspective
OK
Sun Mar 29 19:22:56 EEST 2020
launchesTerminated

Submitted by Francesco ********** on Sat, 04/04/2020 - 15:35

Hello Ivan,

unfortunately, I couldn't repoduce the issue. I've just tested it with a fresh version 2020-03 and a simple java project and it worked for me. The log entries do not show an Error/Exception. The log statements indicate that the plugin noticed the debug launch and the debug termination. It should have switched back to the previous perspective if
1) debugging was started from a (non-debug) perspective and
2) the debug perspective was active when the debugging ended
If it didn't switch back under those conditions, it could be an issue if not the standard debug perspective was used.

I would need specific reproduction steps to investigate further. I've added a contact mail address to the plugin description.

Submitted by Francesco ********** on Wed, 01/16/2019 - 17:25

For those reasons:

1) The bug report:
    a) After I had read the bug discussion, it wasn't clear to me how they wanted it exactly. There are comments about switching to the initial perspective, but comment 33 it says it should switch to the perspective set in the preferences.
    b) It seems to be a very long process. In 2011 there was a patch submitted but it took more than 4 months for someone to look at it. After that nothing happened.
2) I am not familiar with the eclipse internals.

I feared that it might take too long or get bogged down.
By doing it as a plugin it's faster out there (and can be used with older eclipse versions).

If the behavior of the plugin is close enough to what the maintainers want, I would be willing to attempt to write a patch for it.

I thought it would be good to get some feedback and bug reports for the plugin first.