good point.
> The "correct" groupId should be org.apache.commons
Sadly this is true for a few projects like commons.lang, but it's not true for
all projects, since a few commons projects already use the 'correct' groupId.
Also, this approach would not scale in the future.
LieGrue,
strub
+1 for new packages
-0 for x-ng
let's make 1 step back and see the issue from the distance.
What's currently going on is not a simple 'feature addition' which has to be
compatible. It's more about an effort to use a lot of cool features which are
available since java-5 _without_ having to take
