Maybe it is reasonable and better to separate the actual job descriptions from the groovy utils we use to build them. Currently we port changes to various branches if add/fix a generator or add a repository etc.

Repositories
1. Camunda JobDSL Utils: everything under src/ currently (only one master branch)
2. Camunda JobDSL: the jobs/ and view/ directories (branches for different camunda versions)

I'm not sure how to best handle the dependency. I think releases and gradle dependecy is just to much. Maybe git submodule or better subtree is the way to go.