Added support for settings.xml

[jcordes73]

Now in a source project a settings.xml can be provided in the configuration folder similar to JBoss EAP and JBoss Fuse xPaaS images.

[kenfinnigan]

I'm not sure these changes are appropriate given that they're related to Red Hat products.

WildFly Swarm is not a product, only an upstream project.

[jcordes73]

It should be implemented irrespective of community or enterprise, these were just examples. The same is done also for the WildFly STI. Otherwise builds just take too long on OpenShift.

[kenfinnigan]

But you've added profiles for eap repositories, etc.

What is the main reason for needing settings.xml?

[jcordes73]

I can remove the enterprise repos. The benefits of being able to provide Maven settings are:

• Faster build times (from minutes to seconds)
• Ability to provide grouping of repositories
• Ability to provide proxy settinhs

[jcordes73]

So you can disregard this pull request, I will send an enhanced version with the clean-up on the repos later.

[kenfinnigan]

What is it about a settings.xml that improves the build time?

[jcordes73]

Of course you need to override this "template" settings.xml with URLs pointing to your Maven repository (for example Nexus) that can act as a caching proxy as otherwise artifacts are always pulled from the internet when creating new apps.

[jcordes73]

I just removed the enterprise repos ...