Replies: 1 comment 1 reply
-
|
I assume this is a simple bug. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
"Update the classpath settings" button (Manifest Editor Overview) or "Update Java Classpath" dialog (Plug-in Tools->Update Classpath...) unconditionally removes classpath entries of kind="var" (variable), as discovered along PR #497.
Although we don't (seem to) use 'variable' classpath entries in our application here, unconditionally removing feels counter-intuitive.
Is there a specific reason not to preserve them just like the other classpath entries?
Beta Was this translation helpful? Give feedback.
All reactions