-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Update lastnpe EEA to 2.4.0 #16875
Update lastnpe EEA to 2.4.0 #16875
Conversation
Signed-off-by: Leo Siepel <[email protected]>
The problem is that we can't do proper null annotations with EEA. Unfortunately there is no will on Eclipse side to fix that. We would need something like "non-null if argument is non-null". This also applies to |
Is there some kind of link to that discussion? And more important do you have some thoughts on how to proceed in relation to this PR? |
....binding.dsmr/src/main/java/org/openhab/binding/dsmr/internal/device/DSMRDeviceRunnable.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Leo Siepel <[email protected]>
I can't validate this any time soon for the AndroidTV/PhillipsTV bit. Is this a Java 17 update or would this still be backwards compatible to Java 11? I'm about to kill off the 3.x compatibility but I haven't yet so I'm trying to keep that in mind still. |
As far as i know this should be java 11 compatible. Maybe 4.2 is a good point to move on anyway. |
Signed-off-by: Leo Siepel <[email protected]>
Signed-off-by: Leo Siepel <[email protected]>
simplify daikin
Signed-off-by: Leo Siepel <[email protected]>
Signed-off-by: Leo Siepel <[email protected]>
Signed-off-by: Leo Siepel <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine for sensorcommunity
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot! 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM for helioseasycontrol
@openhab/add-ons-maintainers now 4.3 development is started, would be nice to have this merged sooner then later. |
Looks like some new code got added that no longer compiles with the newer EEAs. |
Signed-off-by: Leo Siepel <[email protected]>
Signed-off-by: Leo Siepel <[email protected]>
Signed-off-by: Leo Siepel <[email protected]>
@openhab/add-ons-maintainers ping |
Signed-off-by: Leo Siepel <[email protected]>
Signed-off-by: Leo Siepel <[email protected]>
Signed-off-by: Leo Siepel <[email protected]> Signed-off-by: Patrik Gfeller <[email protected]>
Signed-off-by: Leo Siepel <[email protected]>
Signed-off-by: Leo Siepel <[email protected]>
Resolves: #10396
The reason is that the new version fixes that Optional.orElse can return null values (based on the parameter).
There is quite some code using Optional.orElse expecting the result to be non-null.
In most cases i wrapped the optional in
Objects.requireNonNull(..)
and in some cases i removed the optional.At time of writing bindings A-D have been adjusted and i like to get some feedback before proceeding to fix all.
Edit: Moved on to bindings A - K
JFTR: to be merged after 4.2 release as i cannot test all bindings.