You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Operaton Project forked Camunda 7 and plans to provide an easy migration for potential users, their efforts are open via operaton/migrate-from-camunda-recipe.
One problem is to migrate the dependencies from the Camunda namespace to the Operaton namespace.
While writing test, it occurred that the dependency managent recipes and tooling are not fully managed by the org.openrewrite.recipe:rewrite-recipe-bom artifact.
Needed additions to develop/test Maven and Gradle migrations:
org.openrewrite.gradle.tooling:model
org.codehaus.groovy:groovy, scope test
org.gradle:gradle-tooling-api, scope test
Describe the solution you'd like
Manage the needed dependencies for framework developer to lower the barrier.
Have you considered any alternatives or workarounds?
Manual adding and writing a specially shaped documentation could be a workaround.
Additional context
The text was updated successfully, but these errors were encountered:
What problem are you trying to solve?
The Operaton Project forked Camunda 7 and plans to provide an easy migration for potential users, their efforts are open via operaton/migrate-from-camunda-recipe.
One problem is to migrate the dependencies from the Camunda namespace to the Operaton namespace.
While writing test, it occurred that the dependency managent recipes and tooling are not fully managed by the org.openrewrite.recipe:rewrite-recipe-bom artifact.
Needed additions to develop/test Maven and Gradle migrations:
Describe the solution you'd like
Manage the needed dependencies for framework developer to lower the barrier.
Have you considered any alternatives or workarounds?
Manual adding and writing a specially shaped documentation could be a workaround.
Additional context
The text was updated successfully, but these errors were encountered: