Hi,
What's your Karaf version ? I tested similar scenario with 4.0.4 without
problem.
Did you try to remove data or other folders ?
Generally speaking, kar is an atomic deployment. Prefer to use feature
directly, it's more flexible.
Regards
JB
On 04/27/2016 04:21 PM, Olivier21 wrote:
Hello,
I'm a newbie for Karaf and I have two problems.
1) I installed a kar archive in Karaf via the deploy folder.
2)After, I tested the Web Service and it works fine. The version of all the
OSGI bundle in the archive is "1.0.0" and all the bundles have got a class
"Activator" which display the message "bundle X started in version 1.0.0"
after the deployement.
3) I stopped Karaf
4) I remove the kar archive from the deploy folder
5) I decided to change the release of one of the OSGI bundles to "1.0.1" and
I created a jar file that I copy in the deploy folder. This bundle have got
a class "Activator" which should display the message "bundle X started in
version 1.0.1".
6) I started Karaf
7) The message "bundle X started in version *1.0.0*" is displayed instead of
the message "bundle X started in version *1.0.1*". Hence, this message
appears 2 times because I didn't remove the release "1.0.0" of this bundle.
8) If I stop Karaf then I remove the jar file from the deploy folder then I
restart Karaf, then the message "bundle X started in version *1.0.0*"
doesn't appears any more but the message "bundle X started in version
*1.0.1*" appears 2 times.
Nevertheless, instead of renaming the version "1.0.0" to "1.0.1", if I
rename the version "1.0.0" to "1.1.0" (in the point 5 above), then I started
Karaf (in the point 6 above), the message "bundle X started in version
*1.0.0*" appears firstly (that's normal) followed by the message "bundle X
started in version *1.1.0*". Hence, everything is normal in this case.
*Could you say me why it doesn't work like this in the case of the version
"1.0.1" please?*
For your information, here is an extract of the parent pom :
<dependency>
<groupId>org.omega.wsrest</groupId>
<artifactId>omega-module-service-metier</artifactId>
<version>[1.0.0, 2.0)</version>
</dependency>
<dependency>
<groupId>org.omega.wsrest</groupId>
<artifactId>omega-module-dao</artifactId>
<version>[1.0.0, 2.0)</version>
</dependency>
and here is an extract of the child pom :
<dependency>
<groupId>org.omega.wsrest</groupId>
<artifactId>omega-module-service-metier</artifactId>
<version>1.0.0</version>
<type>bundle</type>
</dependency>
<dependency>
<groupId>org.omega.wsrest</groupId>
<artifactId>omega-module-dao</artifactId>
<version>1.0.0</version>
<type>bundle</type>
</dependency>
All the modules (parents and childs are in the kar archive).
Moreover, I have a second question : in my case, I have a bundle A which is
called by :
- bundle B
- and Bundle C
This is the bundle A which is in my Jar archive. *How to do to say to bundle
B and C to point to the new release of bundle A?* (Until now, I restarted
Karaf ...but I imagine there is another way).
Thank you in advance for your help.
Olivier
--
View this message in context:
http://karaf.922171.n3.nabble.com/Bundle-versioning-tp4046396.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
