[
https://issues.apache.org/jira/browse/BROOKLYN-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235079#comment-15235079
]
ASF GitHub Bot commented on BROOKLYN-250:
-----------------------------------------
Github user sjcorbett commented on the pull request:
https://github.com/apache/brooklyn-server/pull/111#issuecomment-208339865
The test failure is unrelated but interesting -
```
org.apache.brooklyn.entity.stock.BasicStartableTest.testTransitionsThroughLifecycles
(from TestSuite)
Expected: eventually IsEqualTo([starting, running, stopping, stopped]); got
most recently: [starting, running, stopping, stopping, stopped] (waited 1s 4ms
696us 7ns, checked 99)
Stacktrace
java.lang.AssertionError: Expected: eventually IsEqualTo([starting,
running, stopping, stopped]); got most recently: [starting, running, stopping,
stopping, stopped] (waited 1s 4ms 696us 7ns, checked 99)
```
@aledsage Have you seen duplicate states before?
> displayName in location brooklyn.config not being used
> ------------------------------------------------------
>
> Key: BROOKLYN-250
> URL: https://issues.apache.org/jira/browse/BROOKLYN-250
> Project: Brooklyn
> Issue Type: Bug
> Affects Versions: 0.9.0
> Reporter: John McCabe
> Priority: Minor
> Attachments: catalog.png, dropdown.png
>
>
> Observed that the {{displayName}} field populated by the location wizard/yaml
> doesn't appear to be used? For example:
> {code}
> brooklyn.catalog:
> items:
> - id: locationid
> itemType: location
> item:
> type: localhost
> brooklyn.config:
> displayName: locationname
> {code}
> displays as {{locationid}} rather than {{locationname}} (in dropdown lists
> and the catalog page), whereas the following
> {code}
> brooklyn.catalog:
> items:
> - id: locationid
> itemType: location
> name: locationname
> item:
> type: localhost
> {code}
> displays the string set in the {{name}} element.
> If {{name}} isn't present it falls back to using the {{id}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
