You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@plc4x.apache.org by Christofer Dutz <ch...@c-ware.de> on 2024/03/24 10:04:18 UTC
Moving things to the plc4x-extras.git repo
Hi all,
so I just initiated the creation of the plc4x-extras repo and I guess it will be created in a few minutes.
I would propose we keep the naming scheme identical to the main repo:
* Development is done on “develop”
* Releases are merged to “release”
Regarding components that should be moved to the extras repo, how about this:
* plc4c/examples/**
* plc4c/integrations/**
* plc4x/tools/plc4x-server
* plc4go/examples/**
* plc4go/tools/plc4xbrowser
* plc4go/tools/plc4xpcapanalyzer
* (it looks as if plc4go/tools/generator and licenser are tools used for the build)
* plc4j/examples/**
* plc4j/integrations/**
* plc4j/tools/opcua-server
* plc4j/tools/plc4x-server
* plc4j/tools/ui/**
What do you think?
I would propose to keep the directory structure and I would try to replicate the general build as it was in a mono-repo before.
I guess the main repo build will then live with a LOT less managed dependencies and plugins managed.
Chris
AW: Moving things to the plc4x-extras.git repo
Posted by Christofer Dutz <ch...@c-ware.de>.
Guess I’ll leave this thread for another 2-3 days and then start moving things based on my proposal.
Chris
Von: Christofer Dutz <ch...@c-ware.de>
Datum: Sonntag, 24. März 2024 um 11:04
An: dev@plc4x.apache.org <de...@plc4x.apache.org>
Betreff: Moving things to the plc4x-extras.git repo
Hi all,
so I just initiated the creation of the plc4x-extras repo and I guess it will be created in a few minutes.
I would propose we keep the naming scheme identical to the main repo:
* Development is done on “develop”
* Releases are merged to “release”
Regarding components that should be moved to the extras repo, how about this:
* plc4c/examples/**
* plc4c/integrations/**
* plc4x/tools/plc4x-server
* plc4go/examples/**
* plc4go/tools/plc4xbrowser
* plc4go/tools/plc4xpcapanalyzer
* (it looks as if plc4go/tools/generator and licenser are tools used for the build)
* plc4j/examples/**
* plc4j/integrations/**
* plc4j/tools/opcua-server
* plc4j/tools/plc4x-server
* plc4j/tools/ui/**
What do you think?
I would propose to keep the directory structure and I would try to replicate the general build as it was in a mono-repo before.
I guess the main repo build will then live with a LOT less managed dependencies and plugins managed.
Chris