Does the fact that JGroups uses LGPL at the moment (they plan to switch to
APL 'soon') prevent it from being used in Sling?
Cheers,
Stefan
On 7/3/13 3:05 PM, Carsten Ziegeler cziege...@apache.org wrote:
Thanks for taking this up, Stefan.
I think we should also try to close down the first
On Fri, Jul 5, 2013 at 12:18 PM, Stefan Egli e...@adobe.com wrote:
Does the fact that JGroups uses LGPL at the moment (they plan to switch to
APL 'soon') prevent it from being used in Sling?
AFAIK LGPL is a blocker, see [1]
Robert
[1]: http://www.apache.org/legal/resolved.html#category-x
Yep, it's a blocker - so we should use something else or wait and increase
the pressure to make them switch :)
Carsten
2013/7/5 Robert Munteanu rob...@lmn.ro
On Fri, Jul 5, 2013 at 12:18 PM, Stefan Egli e...@adobe.com wrote:
Does the fact that JGroups uses LGPL at the moment (they plan to
On Fri, Jul 5, 2013 at 1:29 PM, Carsten Ziegeler cziege...@apache.org wrote:
Yep, it's a blocker - so we should use something else or wait and increase
the pressure to make them switch :)
I found out today that the switch is complete in the master branch
[1], so we can start using it right now
Thanks for taking this up, Stefan.
I think we should also try to close down the first version of the discovery
api and release this, so other parts of our code can really rely on this
api.
Apart from that, I don't have a strong preference, although it would be
nice to just use Apache stuff :)
Hi,
I've created SLING-2939 [0] to track an additional, 3rd party based
implementation of the discovery.api. The idea is to complement the
discovery.impl (which is ootb, entirely sling-based) with a more mature,
specialized, scalable implementation based on a clustering library. I've
