better resolution of workflow inputs

- prevent confusion with subkeys having dot qualifiers and being omitted when used in sensor/policy definition
- don't coerce a supplier to a map
- allow unknown types under type key in maps, since we now use our deserializers for it
- allow access to selected workflow.util vars even outwith workflow
- return entity predicate where required, and better coercion from boolean to conditions
- remove deprecated findKeys method
- better error messages
- more tests
22 files changed
tree: 31386b7748d000d55c91fc005283bde3be09a891
  1. api/
  2. camp/
  3. core/
  4. karaf/
  5. launcher/
  6. launcher-common/
  7. locations/
  8. logging/
  9. parent/
  10. policy/
  11. rest/
  12. server-cli/
  13. software/
  14. test-framework/
  15. test-support/
  16. utils/
  17. .gitattributes
  18. .gitignore
  19. DEPENDENCIES
  20. Dockerfile
  21. Jenkinsfile
  22. LICENSE
  23. NOTICE
  24. pom.xml
  25. README.md
README.md

Brooklyn

Apache Brooklyn Server Sub-Project

This repo contains the core elements to run a Brooklyn server, from the API and utils through to the core implementation and the REST server.

Building the project

Two 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:server .

Then run the build:

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

Using maven

Simply run:

mvn clean install