Add support setup default initializers for all deployment

This looks up a new configuration options called `brooklyn.deployment.initializers` (comma separated list). If specified on a Brooklyn instance, all deployments will load and execute these initializers. Theses classes are expected to be `EntityInitializer`, if an error occur (either cast or anything else) then the deployment will fail.

The code will try to:
1. load the class from the default class loader.
2. if (1) fails, it will try to load the class from the `TypeRegistry`. This is to allow execution of custom initializers that might be installed in the catalog later on.
3. if (1) and (2) fails, then the deployment is aborted.
1 file changed
tree: 096510c7e13c71bc9f433a87970ad599165afff4
  1. .mvn/
  2. all/
  3. archetypes/
  4. deb-packaging/
  5. dist/
  6. docker/
  7. docker-image/
  8. docker-itest/
  9. downstream-parent/
  10. karaf/
  11. release/
  12. rpm-packaging/
  13. scripts/
  14. shared-packaging/
  15. vagrant/
  16. .gitattributes
  17. .gitignore
  18. DEPENDENCIES
  19. Dockerfile
  20. Jenkinsfile
  21. LICENSE
  22. NOTICE
  23. pom.xml
  24. README.md
README.md

Brooklyn

Distribution Sub-Project for Apache Brooklyn

This repo contains modules for creating the distributable binary combining the server, the ui, and other elements in other Brooklyn repos.

Building the project

2 methods are available to build this project: within a docker container or directly with maven.

Using docker

The project comes with a Dockerfile that contains everything you need to build this project. First, build the docker image:

docker build -t brooklyn:dist .

Then run the build:

docker run -i --rm --name brooklyn-dist -v /var/run/docker.sock:/var/run/docker.sock -v ${HOME}/.m2:/root/.m2 -v ${PWD}:/usr/build -w /usr/build brooklyn:dist mvn clean install

Using maven

Simply run:

mvn clean install