Bugzilla – Full Text Bug Listing
| Summary: | Java Run Configuration are empty after upgrade | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Luca Preziati <luca.preziati> | ||||||||
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> | ||||||||
| Status: | NEW --- | QA Contact: | |||||||||
| Severity: | normal | ||||||||||
| Priority: | P3 | CC: | sarika.sinha | ||||||||
| Version: | 4.19 | ||||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Windows 10 | ||||||||||
| Whiteboard: | stalebug | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 286028 [details]
screehshot with details
Can you check .settings file in your workspace? Is it overridden by the update ? It contains the details of launches. Created attachment 286038 [details]
.setting
I chekc the file, no update present. But sorry in the first window the button is available to run in the second one no. So i think the bug is in the window of run configuration. Otherwise is not visibile in the first window. 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. If you have further information on the current state of the bug, please add it. 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. |
Created attachment 286027 [details] Screenshot of the bug Java Run configuration not appear in in Run Configuration window, so it is not possible to set up variable environment. In the part of the image of left, you can see maven and Java Application run. In Run Configuration there are not any Run Configuration available. That happen after the upgrade from 4.18 to 4.19 version of eclipse. The project are Spring boot microservice and i start from their own main class.