Hello,
as a sequel of the question asked in this thread I’d ask onother one.
You did a great job by forking the camunda project, renamed the packages etc. Wouldn’t it also be an option to just clone the original repository and not change anything about the namespace, packages etc? I.e. just have a clone and develop it further. And have the control over the repository. This would make merges much mor simple IMO. Have you considered this option (I’m sure you have)? Why was it rejected?
Thank you!
This is legally not possible. „Camunda“ is a trademark and the name of the company behind that. It is in their very interest to protect their name and would result in legal issues when something is not in their interest.
@javahippie could give more details here. It has been all clarified with lawyers what can be done and what must be done. This is simply a must here.
Btw. the same happened in the past when jBpm became Activiti, and Activiti became Camunda and later Flowable.
The backports (or “merges,” as you referred to them) will conclude in October 2025. This process has not posed any significant challenges for our project, as we’ve streamlined it as much as possible. We’ve automated most of the work and ensure that all useful commits are thoroughly reviewed and reintegrated.
The reasons behind this transition are twofold. First, there are legal considerations that required us to make this change. Second, there’s a technical limitation: Maven Central does not allow the publication of packages that do not belong to your namespace.
To further ease the migration to the new namespace, we’re actively developing OpenRewrite scripts. These will help simplify the process for users and ensure a smooth transition.