Studio Projects Inheritance

When working with multiple Studio projects, it would be useful to be able to reference other Studio projects from the same organization in a project Application Definition screen.

The target Studio project registries would be filled accordingly, so that it is possible to use configuration from the referenced Studio project (document types for instance), like any other referenced package.

It would be nice to also handle:

• requirements on the referenced Studio project, for deployment as well as runtime definition (see below)
• check of potential dependency cycles
• choice of a given release of the referenced Studio project (currently, the versions of the packages that are referenced in application definition are not taken into account, so they are not part of the package definition built by Studio)
• choice of the referenced Studio project branch

Current workaround consists in:

• pushing a private package release, holding the referenced Studio project corresponding registries
• selecting that package on the Application Definition screen
• adding deployment and runtime requirements manually in advanced configurations:
  In "Modeler > Advanced Settings > XML Extensions" as well as in "Modeler > Advanced Settings > Deployment Extensions":

  <require>studio.extensions.referenced-studio-project-name</require>