Hey guys, sorry for multiple recent question. I'm biting down hard on Sling
right now and hitting tons of learning curve and growing pains.
My problem: If I create a fresh instance of MongoDB, and connect multiple
fresh instances of Sling to it (each running in a separate tomcat instance),
they
Gah - solved myself almost immediately after posting.
For posterity: version 3.5 of commons lang has a different
Bundle-SymbolicName ( org.apache.commons.lang3) in the OSGI metadata of
MINFEST.MF. Simply by bumping to lang 3.5 you'll solve this.
--
View this message in context:
I use Commons tools both version 2 and 3 together in AEM and so it should work.
That said how are you installing Commons lang and which package does need it.
If you have a custom package that needs commons lang 3 then you need to package
it with it
if it is not provided from another package.
I have packages (such as composum tools) that depend on apache commons lang
3.
I have other packages (such as most of the sling itself) that depend on
commons lang version 2.
There are no Java Package namespacing collisions between these packages -
they can both exist in the same JVM safely.
Hi Evgeniy,
On Sun, 2017-01-08 at 13:18 +0300, Evgeniy Fitsner wrote:
> Hello,
>
> is there any plans when Sling 9 will be released?
Are are planning on releasing it :-) The tracking task is
https://issues.apache.org/jira/browse/SLING-6194
To my knowledge we don't have a hard plan, but I
