| commit | e3a16614055f83f68164d6cfe222668710a4f953 | [log] [tgz] |
|---|---|---|
| author | Aled Sage <aled.sage@gmail.com> | Tue Jan 12 16:55:01 2016 +0000 |
| committer | Aled Sage <aled.sage@gmail.com> | Tue Jan 12 16:55:01 2016 +0000 |
| tree | 12c70b6b342b48600990e15bb289c384235bd6b3 | |
| parent | d0581581075b6484a814edccc93963a6c025371d [diff] |
YAML: don’t wrap sub-entities in BasicApplication Previously, any catalog item of type “template” would always be wrapped in a BasicApplication. This was being done in three places. The first is ok; the second two are bad: 1. When deploying a top-level “template” from the catalog. 2. When referring to a “template” catalog item in a member-spec (e.g. for a DynamicCluster) 3. When referring to a “template” catalog item in brooklyn.children.
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.