Support for referencing Java catalog entities in YAML
Aggregate the class loaders of classes involved in the proxy creation.

Should be more generic than the previous approach.
Remove unused var
Remove entitlements TODO (no requirement to do per-entity instantiation); Multiple root entities not to be supported for the time being.
Add a test for a catalog referencing itself.
The build fails when an explicit version is set, with the following
error:
The following artifacts could not be resolved:
io.brooklyn:brooklyn-test-support:jar:0.1.0-SNAPSHOT,
io.brooklyn:brooklyn-logback-includes:jar:0.1.0-SNAPSHOT

Caused by the usage of ${project.version} in the parent dependencies
instead of ${brooklyn.version}
Instead I fixed the bundle version to 0.1.0 with the
maven-bundle-plugin. 

This project is tied to the brooklyn version in a way because its build
depends on the parent pom.
CAMP catalog handling: delete unused code
Fix recursive call (catalog type == java type)
Adds catalog.deleteCatalogItem

- needed for CatalogBundleResourceTest, so that tests don’t interfere
  with each other.
CAMP: handle serviceType “java:” prefix
Add the classloader as per Aled's suggestion.
Remove TODOs, already implemented in CatalogBundleResourceTest
Merge pull request #6 from neykov/osgi

Adress last OSGi merge comments