Re: Feature, conditionally started based on a system capability

Hello JB, thank you for the prompt reply! You can to install the jahia-clustering feature only if org.jahia.cluster "property" is activated, right ? Yes, that's right (like a feature-switch or enabler). I've corrected the syntax for the requirement and it is taken into consideration on

Decanter - Elasticsearch 2.x ?

Hi everyone, Is there any plans/date for the upgrade to Elasticsearch 2.x in Decanter? Regards, Carl -- View this message in context: http://karaf.922171.n3.nabble.com/Decanter-Elasticsearch-2-x-tp4045096.html Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Karaf-4.0.4 - CNF Exception in eclipse link feature.

Hi Erwin, maybe Dynamic-Import could work as a workaround. I gonna check the bundle headers. Regards JB On 02/01/2016 12:53 PM, Erwin Hogeweg wrote: Nope. bundle:install -s

Re: Karaf-4.0.4 - CNF Exception in eclipse link feature.

JB, > maybe Dynamic-Import could work as a workaround. Thanks, that worked. it added this to the headers: DynamicImport-Package = * Export-Package =

Re: Karaf-4.0.4 - CNF Exception in eclipse link feature.

Nope. bundle:install -s 'wrap:mvn:org.apache.aries.jpa/org.apache.aries.jpa.eclipselink.adapter/2.3.0/$Import-Package=org.apache.aries.jpa.eclipselink.adapter.platform' Import-Package = javax.persistence;version="[2.1,3)", javax.persistence.spi;version="[2.1,3)",

Re: Decanter - Elasticsearch 2.x ?

Hi Carl yes: I already something ready, but I have to update the appender to use the REST API instead of the TransportClient (to be able to work with Elasticsearch 2.x and 1.x). However, I'm still working on Kibana 4.1 embedded mode (due to node.js dependency). Regards JB On 02/01/2016

Re: openjpa 2.4.1

Yes, Mark (Struberg) and Romain said they gonna release it very soon (this week). Regards JB On 02/01/2016 07:42 PM, Pratt, Jason wrote: Jb – any response back yet? jason *From:*Pratt, Jason *Sent:* Tuesday, January 26, 2016 1:46 PM *To:* 'user@karaf.apache.org' *Subject:* openjpa 2.4.1

Re: Karaf insisting on loading older version of feature?

I just tried it again on a totally vanilla karaf instance, newly decompressed from the tar.gz: feature:install spring-dm-web results in both Spring 3.1.4 and Spring 3.2.14 being loaded: karaf@root()> list -t 0 -l | grep spring 58 | Active | 30 | 4.0.4|

Re: Karaf insisting on loading older version of feature?

I just installed the spring-dm feature, so the spring-dm-web probably installs transitively another feature requiring spring 3.1 (but not 3.2). With feature:install -v shows that spring 3.1 is installed just after pax-web features. So, let me check the resolver messages. Regards JB On

Re: Karaf insisting on loading older version of feature?

Here is another odd thing: if you `feature:install http` *first* all the pax-web bundles (as well as jetty and so on) load, with no Spring dependencies. If you *then* feature:install spring-dm-web, it loads *without* installing the Spring 3.1.4 bundles. In addition, I was able to copy the

Re: Karaf insisting on loading older version of feature?

I think it is via the resolver (due to req/cap). Regards JB On 02/01/2016 04:45 PM, Raman Gupta wrote: Here is another odd thing: if you `feature:install http` *first* all the pax-web bundles (as well as jetty and so on) load, with no Spring dependencies. If you *then* feature:install