Arjans,
Commits to the release branches and specifically EE4J_8 need to be approved by a spec lead (ie Stuart or myself), so you really should not have merged #218 (even though they are good fixed and I would have approved it).
Mark,
I hear you that it would have been good to get some other changes into 4.0.2, but the intention really appears to be just minimal changes to: a) build artifacts from new repos; b) update licenses; c) new maven coords; d) new osgi coords; e) nothing else. So let's get a 4.0.2 out on these terms and then quickly get a 4.0.3 out with the little fixes we want to get in (basically master as it is now).
Also as an aside, just remember that this is not apache and that -1 votes are not binding. However, having said that, I do find the whole -1, -0, +0, +1 approach a good way to express strength of feeling on a particular issue, so using it here is good... just so long as we all realise a -1 is not as binding as it may be in apache (or elsewhere).
All,
Is the current state of EE4J_8 after the merge of #218 OK for release?