Date: Fri, 29 Mar 2024 08:45:32 +0000 (UTC) Message-ID: <749142968.1501.1711701932629@b9607565de67> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1500_475699860.1711701932628" ------=_Part_1500_475699860.1711701932628 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
odlparent
ODL Root Parent provides three features in Beryllium release,= which are repackaging of widely-used third party dependencies:
N/A
None
ODL Root Parent provides mostly build-related infrastructure = and a centralized place for managing versions of third-party dependencies. = While it does not introduce security risks itself, third-party artifacts ma= y introduce security considerations, which need to be analyzed and taken in= to account.
ODL Root Parent has a small Java component, which is modified= Karaf plugin. This shows up in Sonar. This component is exercis= ed by odlparent-provided features and does not have unit tests. Reported So= nar issues are coding-style-related and will be addressed in the next relea= se.
This is the last release declaring artifacts from eclipseSDK3= 81. These components are outdated and at least some of them are not Java-8 = compatible. Furthermore many of these are not used within OpenDaylight. Unu= sed artifacts will be removed and the remaining ones will be replaced by th= eir org.eclipse.tycho equivalents.
ODL Root Parent has currently 5 oustanding issues= . None of these prevent the functionality provided from working. One of tho= se deals with SingleFeatureTest coherence with user experience. Two track i= mprovements to packaging collateral (CONTRIBUTING and similar). One deals w= ith JaCoCo/Powermock integration. One tracks an ugly warning we get for pac= kaging features.
Not applicable.
We have started this release cycle with an empty release plan= and all improvements have been contributed outside of planning. This means= the project was always on schedule. While this has not lead to any wide-sp= read breakage, as the number of our downstreams increases and becomes more = diversified, we will need to plan our major features and third-party upgrad= es in a structured way.