Make dependency on java.desktop optional #1182
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is only one place in commons-lang where anything from
java.desktop
is used, and that isAbstractCircuitBreaker
.This changes that code to lazily initialize its internal
PropertyChangeSupport
. This makes it so that it is safe to initialize and use that class withoutjava.desktop
on the module-path.Upsides:
Downsides:
null
instance ofPropertyChangeListener
without depending on thejava.desktop
module, in which case the behavior of the method will change from "ignores null" to "fails"java.desktop
present. Currently I am validating manually like soBefore
After