Separate the MortgageApplication into a separate repository

[Crosswind]

I stumbled across this a couple of weeks ago when we started to set up a proper development environment for developing our Groovy/DBB scripts in Eclipse. I realized that Eclipse always imports a second project which happens to be the MortgageApplication because it contains a .project file and Eclipse looks for those.

That by itself is not a huge issue and can be worked around. It did however spark the idea that from a repository management point of view it would make a lot more sense to separate this into its own repository. Right now it is hidden in the samples directory which makes it a lot less intuitive to e.g., start a new project based on the sample. It would also declutter the commits done to the actual build logic from samples.

We don't work with the MortgageApplication as a sample application when using DBB/zAppBuild. For someone that is starting out with zAppBuild this might be different but that person should rather be instructed to put zAppBuild in one place, then clone the MortgageApplication separately and then work off of it as you would do with every other project. (i.e., in real life you would also not have the application checked in with the build logic).

What do you think?