Support multiple quickstarts in a single Git repository

[gastaldi]

Right now the indexer requires a single repository per quickstart. It would be nice if we could support multiple quickstarts in a single repository, thus giving more power and autonomy to the team

[gastaldi]

Dependencies between quickstarts in a single repository may not be possible.

[jstrachan]

Its easier for users to understand & fork if each quickstart is in a separate repo - it also avoids putting too much magic in parent poms that gets lost if the user generates a new stand alone quickstart from it. Though its harder for maintainers to keep things in sync and up to date ;)

We've been through this journey on the fabric8 quickstarts; we started in a single repo and got more microservice-y and so now have separate repositories.

It turns out the hardest part was aligning versions and testing which we managed to automate via CD: https://github.com/fabric8io/fabric8-maven-dependencies/

[gastaldi]

Generating an effective pom may be a good idea to resolve project parent relationships See: http://maven.apache.org/plugins/maven-help-plugin/effective-pom-mojo.html

[jstrachan]

Maybe - though that might remove all maven properties from the Pom.xml too. It's probably simpler to just curate stand alone Pom.xml files and keep their versions in sync via CD pipelines. It's worked really well for us in fabric8 - it also means each git repo is forkable & useable directly as well

[ALRubinger]

This issue is about giving implementing projects the freedom to dictate their own repo structure. At the moment, our setup will not work properly with the entire jboss-eap-quickstarts bank as they have N projects in one repo.