Hi Thiago,
As a programmer, I would say: Use the shorter one, having to type less is always welcome ->
org.eclipse.dt.{project_name}.
Looking from the standpoint of already established projects (org.eclipse.basyx), a change of the groupId is not favorable. Do you
expect to change those projects to the new groupId?
Greetings,
Tobias
Von: dt-pmc <dt-pmc-bounces@xxxxxxxxxxx>
Im Auftrag von Weber Martins, Thiago
Gesendet: Freitag, 12. August 2022 10:39
An: dt-pmc@xxxxxxxxxxx
Cc: aas4j-dev@xxxxxxxxxxx
Betreff: [dt-pmc] Apache Maven Central groupID for Eclipse Digital Twin TPL
Dear PMC colleagues,
in this thread I would like to discuss and agree on a groupID for Eclipse Digital Twin TPL.
Background: we use Apache Maven Central to publish java artifacts. As Eclipse Digital Twin TPL, we can define a groupID that can be used by all projects within the top level to standardize and
to make easier to associate published artifacts to the overall picture.
My suggestion is that we use the following groupID:
org.eclipse.digitaltwin.{project_name}
For example, for Eclipse AAS4J the groupID would be
org.eclipse.digitaltwin.aas4j.
Would you agree with using
groupID: org.eclipse.digitaltwin.{project_name}?
An alternative would be
org.eclipse.dt.{project_name}.
Please, let me know if you guys are ok with it until 26.08.2022 as we need this to prepare the releases for AAS4J. I case you agree, I would
document this decision.
Thanks!
Best,
Thiago
Best Regards / Beste Grüße,
Dr.-Ing. Thiago Weber Martins
Product Management – Digital Twins (Open Source & Standards)
PE DSC Manufacturing and Industrial IoT Product Management | Standards SE
SAP SE, Dietmar-Hopp-Allee
16, 69190 Walldorf, Germany
M +49 151 44614348 | E thiago.weber.martins@xxxxxxx
Join me online:
LinkedIn
Pflichtangaben/Mandatory Disclosure Statement: www.sap.com/impressum