Need a means to allow for different sets of runtime libraries for a component configuration

For example, the Oracle component needs to deal with different versions of Jar files for the database.

Here is how we will do it:

1. Use maven profiles for different sets of dependent jars
2. Pre-generate maven dependencies based on profiles (for performance - later)
3. Have a property type of “profile” to allow the possible values to be populated
4. Have a call to the runtime to specify the desired profile
5. Have a class loader that isolates the loading of the dependent stuff (Francois may have provided).

We also have another requirement from the Studio, it is the possibility for the Component serfice client to specify the jar they want to use instead of the one registered in the component itself.