A short update on the release. The downloadables are rolling out to the
mirror network, the Maven artifacts are available, and the main website
"download" page is updated.
However the 0.9.0 user guide is not yet uploaded - it's huge, and hotel
wifi is not the fastest or most reliable (even when
I've pushed the artifacts to the release area so the mirror network will be
picking them up now. So I'm afraid I don't think we can change it now...
It sounds like this bug is not going to affect lots of users (correct me if
I'm wrong) so would be candidate for a 0.9.1 release. We can kick that
Aled,
OK, I think we can live with that caveat. I will update Clocker to make
sure it doesn't trigger this issue for now.
Andrew.
On Tue, 12 Apr 2016 at 14:19 Aled Sage wrote:
> Hi Andrew, all,
>
> This does *not* sound like a blocker to me.
>
> To give some more
Hi Andrew, all,
This does *not* sound like a blocker to me.
To give some more background, the RebindManager.forcePersistNow method
fails if persistence is disabled.
The reason Andrew hit this is he is using the
`SoftLayerSameVlanLocationCustomizer` added in [1]. This calls
forcePersistNow,
Oops.
I was testing Clocker this morning with the 0.9.0 code, using persistence
and the new SoftLayer VLAN code and have discovered an issue with
RebindManager, which is that if forcePersist is called this gives an NPE if
no persister has been set. The (very simple) fix is in
The vote for releasing Apache Brooklyn 0.9.0 [rc4] passed with 3 binding
+1s, 1 non-binding +1s, and no 0 or -1.
Vote thread link:
https://mail-archives.apache.org/mod_mbox/brooklyn-dev/201604.mbox/%3CCABQFKi2rBXoGSD5MoAbePJx71RD7KZZx1nbPO-sjuGk45HYvyA%40mail.gmail.com%3E
Binding +1s:
Andrea