ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: OSGi Manifest headers and feature repository pushed (IGNITE-1527)
Date Wed, 11 Nov 2015 01:52:17 GMT
Thanks Raul, this is great!

Can you please describe again the philosophy between choosing a fragment or
a bundle for Ignite dependencies. I couldn’t fully grasp it from your


On Tue, Nov 10, 2015 at 4:17 PM, Raul Kripalani <raulk@apache.org> wrote:

> Hi all,
> Just to inform you that I've pushed the POM changes to generate the OSGi
> Manifest for all Java modules except: gce, cloud, hadoop, log4j2, spark,
> yarn, mesos, as the prove a bit more difficult for different reasons each.
> Some modules are bundles (e.g. mqtt, zookeeper, kafka, etc.) while others
> are fragments (indexing, jta, geospatial, spring, ssh). The criteria to
> choose between bundle or fragment was whether or not the module contained
> internal processors that ignite-code would have to discover.
> I also created a features repository under modules/osgi-karaf/features.
> If you perform a complete build of the ignite-1527 branch, you should be
> able to install the different modules via the features repository. It has
> been tested against Karaf 4.0.2:
>     karaf@root()> feature:repo-add
> mvn:org.apache.ignite/ignite-osgi-karaf-features/1.5.0-SNAPSHOT/xml/features
>     karaf@root()> feature:install ignite-core
>     karaf@root()> feature:install ignite-mqtt
> The ignite-log4j feature spits out a strange message which I'll debug
> tomorrow.
> Regards,
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message