Bug 553075 - Shortcut "Alt-Shift-X, B" for Run As Spring Boot App does not work after application startup
Summary: Shortcut "Alt-Shift-X, B" for Run As Spring Boot App does not work after appl...
Status: CLOSED DUPLICATE of bug 218881
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.13   Edit
Hardware: PC Windows 10
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-14 15:09 EST by Chris Spencer CLA
Modified: 2020-01-03 05:11 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Spencer CLA 2019-11-14 15:09:18 EST 
When I first open my work space and click a project in the Project Explorer, and use alt-shift-X, B nothing happens. But after I right click open the context menu, it works. 

It looks like the shortcuts are loaded only after a user "activates" the menu or something.
Comment 1 Paul Pazderski CLA 2019-11-14 15:56:11 EST 
Could you please try the following steps (without opening context menus):

 1. open your workspace
 2. switch to debug perspective
 3. optional switch back to your start perspective
 4. start your project with Alt+Shift+X, B

Same result?

Beside are you sure the project is not started or just not visible. I suspect this is related to bug 239217.
Comment 2 Paul Pazderski CLA 2019-11-15 05:13:22 EST 
Found time to test it myself. The project indeed does not start if Alt+Shift+X, B is used and org.eclipse.debug.ui plug-in is not loaded.

This seem to be limited for this specific shortcut family. Starting the spring boot app from Boot Dashboard works even before debug.ui plug-in is loaded.

And most important it is not a spring specific problem. I can reproduce the same problem with Alt+Shift+X, J to run a Java application.
Comment 3 Paul Pazderski CLA 2020-01-03 05:11:05 EST 
Bug 218881 came up which is the same problem as this one. I've added the progress I made working on this (not much) in bug 218881 comment 28.

*** This bug has been marked as a duplicate of bug 218881 ***