Not sure of that :)
It depends what we stand for feature update.
I'm working on ACE around Karaf feature update and lifecycle. I think
that we need to dig on that, feel free to complete the brainstorming
wiki page :)
Regards
JB
On 01/26/2011 05:02 PM, Charles Moulliard wrote:
Here is my two pence (deux centimes in French) idea.
If we provide a new KAR archive containing bundles already installed,
then we should update automatically bundles no matter what is the
version number of the bundle. This philosophy is similar to what we
have when deploying WAR or EAR projects
On Wed, Jan 26, 2011 at 3:30 PM, Adrian Trenaman<trena...@progress.com> wrote:
Hmmmm.
If you deploy a new KAR, then the existing bundles *shouldn't* be updated if
they're already deployed, IMHO. They should only be deployed if they are a
new version of the bundle. Am thinking that in production, bundles with the
same version should be identical, no? We shouldn't allow sneaky updates
under the version number - or should we?!
On 26/01/2011 14:27, Charles Moulliard wrote:
The missing piece that we have concern updating mechanism if I provide
a new KAR archive, the already deployed bundles will not be updated. I
think that this is possible right now with EBA archive.
On Wed, Jan 26, 2011 at 2:57 PM, Adrian Trenaman
<adrian.trena...@googlemail.com> wrote:
Answers inline!
On 26/01/2011 13:51, Charles Moulliard wrote:
ok.
So what do you put in the KAR archive, all the bundles required by
your project + features describing your project bundles to be deployed
and their<features> dependencies with by example camel-jms,
hibernate, mysql-driver, ... ?
Yup! Your application, and all of it's bundle dependencies, can be
packaged
into the KAR.
Do we have a maven plugin to generate the KAR archive like we have
with Aries EBA ?
I have a JIRA open to make a nice maven plugin to do this - for now
though,
we have to live with using a selection of existing Maven plugins to
achieve
our goal - much as how we currently package Karaf / ServiceMix using the
features file to pull down all the dependencies for the system/ folder
before Zipping them up as either .tar.gz or .zip.
On Wed, Jan 26, 2011 at 2:08 PM, Adrian Trenaman
<adrian.trena...@googlemail.com> wrote:
Hi Charles!
The Karaf file *does* include bundles - it's really a collection of
features
descriptors and bundles that can be deployed together easily.
I think the idea will be to pursue a standards based approach (perhaps
based
on Aries EBA and Karaf features) in the future!
Best,
Ade.
On 26/01/2011 12:41, Charles Moulliard wrote:
Hi Ade,
From what I read in the next post of my email, kar only includes
features xml file(s) and no bundles. To deploy an archive containing
bundles we should use eba archive of project Aries.
Regards,
Charles
On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
<adrian.trena...@googlemail.com> wrote:
The purpose of the Kar file is to facilitate easy packaging and
deployment of Karaf features. A feature can have its own bundles
*and*
all its dependencies placed in a Kar; then, when the Kar archive file
is dropped into a deploy directory, the bundles are extracted to the
local drive in a psuedo-Maven directory structure, and any features
files therein are automatically registered in the runtime. This makes
deployment of Karaf solutions easier, particularly when on production
machines where Maven resolution is not possible.
On 24/01/2011, Charles Moulliard<cmoulli...@gmail.com> wrote:
Hi,
What is the purpose of the archive kar that we can deploy now on
Karaf
? Benefits ?
Regards,
Charles Moulliard
Sr. Principal Solution Architect - FuseSource
Apache Committer
Blog : http://cmoulliard.blogspot.com
Twitter : http://twitter.com/cmoulliard
Linkedin : http://www.linkedin.com/in/charlesmoulliard
Skype: cmoulliard
