Henri Yandell wrote
On Wed, Apr 9, 2008 at 7:52 AM, Niall Pemberton
Perhaps if its going to be a
while before 3.3 release gets out, then we could just release
Collections 3.2.1 which is just 3.2 re-packaged ready for OSGi. I
could do that if 3.3 is going to be delayed.
Might be worth it.
Just curious, what's the current state? In Apache Sling we would need an
OSGi enabled release in two weeks :) Now, don't get me wrong, I don't
want to push or force you to do a release (especially as I'm not able to
help with the open issues). I would just like to know, if it might be
possible
On Wed, Apr 9, 2008 at 1:17 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
Just curious, what's the current state? In Apache Sling we would need an
OSGi enabled release in two weeks :) Now, don't get me wrong, I don't want
to push or force you to do a release (especially as I'm not able to help
On Wed, Apr 9, 2008 at 7:52 AM, Niall Pemberton
[EMAIL PROTECTED] wrote:
On Wed, Apr 9, 2008 at 1:17 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
Just curious, what's the current state? In Apache Sling we would need an
OSGi enabled release in two weeks :) Now, don't get me wrong, I don't
On 19/03/2008, James Carman [EMAIL PROTECTED] wrote:
On 3/19/08, Henri Yandell [EMAIL PROTECTED] wrote:
* Specifically for James Carman - how does Dave's patch to your
COLLECTIONS-194 look?
I would rather see it with the nopTransformer(), personally. This
would remove the null checks
Here's a peek at some of the interesting issues in the 3.3 TODO list
that need discussion:
* COLLECTIONS-238 - Allowing ExtendedProperties to have empty values.
ie) foo= would result in a key of foo existing.
Is anyone concerned about backwards compatibility with that? I'm happy
with it - it
On 3/19/08, Henri Yandell [EMAIL PROTECTED] wrote:
Here's a peek at some of the interesting issues in the 3.3 TODO list
that need discussion:
* COLLECTIONS-238 - Allowing ExtendedProperties to have empty values.
ie) foo= would result in a key of foo existing.
It's not just that the key
