It's not a bug, it's by design. If you remove the data folder (so you
remove the features state), the KarDeployer won't take the kar file as
the .timestamp file means that the Kar has been already deployed (it's
to prevent to uncompress/install features from the Kar file everytime
that the file is pooled).
So a simple workaround is to remove the .timestamp before startup (it
will force the uncompress/install features from the kar file).
Regards
JB
On 09/10/2012 05:43 PM, Christian Schneider wrote:
I think it should simply work. So this is probably a bug that we did not
yet see. Can you open a jira issue? Ideally using a fresh karaf with
just the clean option set. So we do not need your custom distro to see
the problem.
Christian
Am 10.09.2012 16:59, schrieb Giacomo Coletta:
Well yes, i use the org.osgi.framework.storage.clean=onFirstInit
property in config.properties, but i need it.
Any workaround to start each time a clean Karaf AND reinstall the
Kar each time ?
Thank you in advance
Giacomo
---------- Forwarded message ----------
From: *Christian Schneider* <[email protected]
<mailto:[email protected]>>
Date: 2012/9/10
Subject: Re: Kar seem to work only once in Karaf based distribution
To: [email protected] <mailto:[email protected]>
Normally the OSGi framework remembers the installed and started
bundles. So after a restart of karaf you should not need to install
the kar again as all bundles should still be there.
I assume that in your distribution you perhaps start a clean OSGi
framework each time which would not happen with a fresh Karaf.
Christian
Am 10.09.2012 13:20, schrieb Giacomo Coletta:
Hi,
I just upgraded to karaf 2.2.9 and tried for the first time to
deploy a feature packaged into a Kar into my karaf based distribution.
I found out that if i put my kar into the deploy folder and start
karaf the feature is installed and started at the first start, but
if i stop and restart karaf the feature isn't installed anymore.
After a few trials, i found out that in order to have the feature
installed again, is sufficient to delete the empty file created at
the kar installation into the folder system/.timestamps and
restart karaf.
Moreover, this strange behaviour only occurs in my karaf based
distribution. If i deploy my kar into a brand new 2.2.9 karaf,
this is normally installed at every restart.
Any idea about the possible cause ?
Thanks
Giacomo
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Divisionhttp://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
