GitHub user ahgittin opened a pull request:
https://github.com/apache/brooklyn-server/pull/62
does not create a localhost named location automatically
the location-add-wizard which @tbouron is working on will make it easy for
users to do this, and there is no reason `localhost` should be added specially
(and good reasons why it shouldn't as it is not representative and it is
error-prone!)
i suggest this be tested and reviewed as part of @tbouron's WIP, and merged
only at the same time as his. (if this lands in time for 090 great but not
needed. probably confusing for a user to merge this PR without the wizard.)
we should also update the release notes with something like the following
explaining the compatibility break:
```
6. The named location `localhost` is no longer automatically added by
default on a fresh Brooklyn install.
Instead UI users are directed to a location wizard where they can configure
their targets, including localhost.
If you require `localhost` to be available on boot, define it as a named
location in `brooklyn.properties`
or the default catalog. (The property
`brooklyn.location.name.localhost=localhost` is usually sufficient.)
If you want a location named `localhost` afterwards, simply add it to your
local catalog using the wizard.
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ahgittin/brooklyn-server no-localhost-default
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/62.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #62
----
commit d332bcc4d60868736716990660f388c648dd8546
Author: Alex Heneveld <[email protected]>
Date: 2016-03-14T16:53:54Z
does not create a localhost named location any longer. the wizard (coming
soon) will do this for us.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
