You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2020. It is now read-only.
Looking at the report generated by openhab/static-code-analysis#283, I see that several packages in org.eclipse.smarthome.ui bundle depend on packages in the Full JRE :
org.eclipse.smarthome.ui.chart depends on java.awt.image
org.eclipse.smarthome.ui.internal.chart depends on java.awt.image
org.eclipse.smarthome.ui.internal.chart depends on javax.imageio
org.eclipse.smarthome.ui.internal.chart depends on javax.imageio.stream
org.eclipse.smarthome.ui.internal.chart.defaultchartprovider depends on java.awt
org.eclipse.smarthome.ui.internal.chart.defaultchartprovider depends on java.awt.image
It might make sense to split the chart support to a separate bundle and mark it with an exception (only working with full JRE).
But then again, there wouldn't be much left in smarthome.ui but the ItemUIRegistry/Provider, which itself depends on Xtext/EMF/etc. and thus isn't really applicable for constraint devices either - this should change in the context of #5337, so maybe it makes sense to wait for these steps.
@svilenvul tl;dr: I would suggest to add an exclusion for this check for this bundle.
Looking at the report generated by openhab/static-code-analysis#283, I see that several packages in
org.eclipse.smarthome.ui
bundle depend on packages in the Full JRE :This is a violation of C.1 in the ESH coding guidelines https://www.eclipse.org/smarthome/documentation/development/guidelines.html#c-language-levels-and-libraries.
The text was updated successfully, but these errors were encountered: