Description of problem:
In case there are inter-dependencies between projects in single git repo, the internal BC build fails after cloning that repo, throwing undesired exceptions in the log. This seems to happen, because BC builds the projects (in the cloned repo) based on alphabetical order. So in some cases the build fails, because the one of the projects depends on not yet built project.

I think we could extend the BC to scan the projects in the newly cloned repo, create correct build order based on the inter dependencies between the projects and then build the modules in that order. This way, everything would work out of the box for the users.

This is not really a major issue as users can always build the projects manually in correct order. But throwing the exceptions after the repo clone may certainly scare the users to think that something is very wrong.


Version-Release number of selected component (if applicable):
6.1.0.ER6


Steps to Reproduce:
0. Make sure you don't have any artifacts with prefix org/jboss/quickstars/brms in your local maven repo
(if you do, you most probably won't see the build error)
1. Clone new repo from https://github.com/jboss-developer/jboss-brms-repository
2. See the server log. 


Actual results:
Exceptions in server log, saying that one of the projects can not be built.


Expected results:
All projects are built successfully.


Additional info: