Date: Thu, 28 Mar 2024 12:35:20 +0000 (UTC) Message-ID: <1066774918.1399.1711629320585@b9607565de67> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1398_2088596466.1711629320584" ------=_Part_1398_2088596466.1711629320584 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This project hosts OpenDaylight example project templates, in= itially in the form of Maven archetypes.
The initial version of this Maven archetype originally existe= d in the controller project, but technical discussions on the Kernel projec= ts call have determined that in order to automatically self test this arche= type, it can no longer live in the controller project, because the archetyp= e also depends e.g. on the netconf project (and possibly others in the futu= re), which the build of the controller project cannot depend on in autorele= ase (see https://git.opendaylight.org/gerrit/#/c/67833/).
Further to the Description given above, the Archetypes projec= t is in principle open to contributions from any ODL project for additional= archetypes from them specific to their project. The Archetypes project com= miters themselves will obviously not be working on such additional archetyp= es themselves, or even request such contributions (other projects "push", t= he Archetypes project does not "pull"). But for each such contribution, we'= ll have to ask the question why such additional archetypes cannot instead s= imply be hosted within the respective project - which would be preferable. = For the controller project there is a technical reason, noted above.
All archetypes in this project must be "self testing" (like t= he one that will be moved from controller will be). In case that such addit= ional archetypes from other projects which cannot be hosted in such project= s break the self testing build of the Archetypes project due to changes in = their respective upstream projects, then the Archetypes committers will com= ment out the respective additional archetypes, and let the contributors of = those projects un-comment them.
This Archetypes project may publish a new archetypes parent P= OM to make it easier for other projects to create self testing archetypes i= n their projects.
Active:
Emeritus:
See below for who is, or will be working on this effort.
Who would be the initial committers to the project?
This proposal is coming from an existing open source codebase= in the ODL controller project.
Sure, as it's just a move of existing code from the controlle= r project to a new git repo for technical reasons.
Getting Started for Users
Getting Started for Developers
Requirements<= /span>