Hi Greg,
Yes, it means we are in the same situation as before with blueprint-core
1.5.0.
So, I don't think it makes sense to let the release if we don't actually
fix the "expected" issue ;)
I would go to -1 then.
WDYT ?
Regards
JB
On 04/10/2016 08:52 PM, Grzegorz Grzybek wrote:
Hello
Unfortunately Jean there's tiny little change to blueprint-cm (handlers are
proxies). blueprint-parser and blueprint-core are ok.
Here's PR to make `CmNamespaceHandler instanceof NamespaceHandler2` work:
https://github.com/apache/aries/pull/43
There *is* problem with Felix connect however (camel-test-blueprint tests
run generally fine, but have now the same timing issue when
CmNamespaceHandler is registered after ExtNamespaceHandler)... `Bundle
extBundle = FrameworkUtil.getBundle(PlaceholdersUtils.class);` doesn't
work, because we have flat classloader... I don't think this should hold
the release however.
so my non-binding vote is [0].
regards
Grzegorz Grzybek
2016-04-09 21:17 GMT+02:00 Jean-Baptiste Onofré <[email protected]>:
Hi all,
in order to fix ARIES-1503 (severe issue), I staged the following
artifacts:
* blueprint-parser 1.5.0
* blueprint-core 1.6.1
* blueprint-cm 1.0.9
Staging Repository:
https://repository.apache.org/content/repositories/orgapachearies-1065/
Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)
This vote will be open for at least 72 hours.
Thanks,
Regards
JB
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
