Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Eclipse Run Configuration - Use Temporary Jar becomes secretly unchecked #1248

Open
toddfroyland opened this issue May 6, 2024 · 1 comment
Assignees
Labels
for: eclipse something that is specific for Eclipse status: needs-investigation type: bug

Comments

@toddfroyland
Copy link

In Eclipse Run Configurations, spring Boot App, modifying anything on any tab causes the "Use temporary JAR to specify classpath" checkbox on the Classpath tab to become unchecked, although it still shows as checked. Unchecking the box does not cause the "Apply" button to activate. Checking the box again allows you to click on "Apply". This ritual, uncheck, re-check, click Apply, must be done every time a configuration change is made.

To Reproduce

  1. Create a Spring Boot App run configuration that has the "Use temporary JAR to specify classpath" box on the Classpath tab checked.
  2. Save the configuration.
  3. Edit the configuration.
  4. Add, delete, or change something on the Environment tab. Click "Apply" there.
  5. Switch to the Classpath tab. Notice that the "Apply" button is grayed out.
  6. Uncheck the "Use temporary JAR to specify classpath" checkbox. Notice that the "Apply" button is still grayed out.
  7. Check the "Use temporary JAR to specify classpath" checkbox. Notice that the "Apply" button is now available to select

This has been an issue for several years. Since I just upgraded to the latest Eclipse (2024-03) and Spring Tool Suite 4 (4.22.0.202403071427), I thought I should finally report it.

Exported launch configuration attached.

DashboardBoot.launch.txt

@martinlippert
Copy link
Member

@toddfroyland Thanks for reporting this and the details steps how to reproduce this. I can clearly reproduce this on my end as well... :-) So let's get that fixed for the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: eclipse something that is specific for Eclipse status: needs-investigation type: bug
Projects
None yet
Development

No branches or pull requests

3 participants