commit | add81aada1d5da340248f03c6438585d4c7aea5c | [log] [tgz] |
---|---|---|
author | Alex Heneveld <alex.heneveld@cloudsoftcorp.com> | Thu Jan 14 13:36:05 2016 +0000 |
committer | Alex Heneveld <alex.heneveld@cloudsoftcorp.com> | Thu Jan 14 14:43:01 2016 +0000 |
tree | 4c731759564a1df499ce5c89d9953fce2008272d | |
parent | 70ed345e4b4cb992d92f363f250000b4c00558ae [diff] |
in AbstractApplication, don't infer locations to pass to start(...) with this, locations defined on an app are no longer inserted automatically by BasicApplication.start(). this is because locations are now normally defined on yaml. entities typically prefer a location if supplied to start(...), but if none are supplied there they look in local configuration and then ancestor configuration. if BasicApplication passes their configured location to the start method, that is trumping any location defined on they descendant entity, which is probably not desired. if an entity does not define a location, there is no change to behaviour as it looks up ancestor location regardless. but this fixes a bug where if a location A is defined on an application, and another location B defined on a particular entity in that application, the entity now uses B whereas previously it was using A. this makes explicit entity startup behaviour consistent with how an entity spec used in a cluster works (which has and still prefers the location defined in the entity spec).
This is the historical incubator repo for Apache Brooklyn.
The sub-directories in this project correspond to multiple separate repositories in apache. (The link above to brooklyn/
started life exactly as a copy of brooklyn/
in this folder, as an uber-project for the others, including the server
and the ui
.)
The code can be built with a:
mvn clean install
This creates a build in usage/dist/target/brooklyn-dist
. Run with bin/brooklyn launch
.