Hi JB, I did test again. I was wrong with 4.2.9. The hot deployment works with 4.2.9 but it didn't work with 4.2.7. So far no further investigation needed with the current version.
Btw .. when 4.3.0 will be released? Best Gerald > Jean-Baptiste Onofre <[email protected]> hat am 21.08.2020 15:43 geschrieben: > > > Same behavior with Karaf 4.2.8 ? > > I will try to reproduce (Karaf 4.2.9 is affected by the Felix FileInstall > issue fixed now). > > Regards > JB > > > Le 21 août 2020 à 15:17, Gerald Kallas <[email protected]> a écrit : > > > > I'm using a vanilla Karaf 4.2.9 with some (Camel) features installed. > > > >> Jean-Baptiste Onofre <[email protected]> hat am 21.08.2020 15:11 > >> geschrieben: > >> > >> > >> Hmmm, it should work (and I’m pretty sure it works for me). > >> > >> Which Karaf version are you using ? With which framework (Felix or > >> equinox) ? > >> > >> It could be related to a caching issue. > >> > >> Regards > >> JB > >> > >>> Le 21 août 2020 à 14:52, Gerald Kallas <[email protected]> a écrit : > >>> > >>> I have one with a separate Activator class, same behaviour. > >>> > >>> As I mentioned, with Apache Servicemix this kind of update works (same > >>> jar files). > >>> > >>> package de.ag.cas.eib.mapping.smx; > >>> > >>> import org.apache.commons.logging.Log; > >>> import org.apache.commons.logging.LogFactory; > >>> import org.osgi.framework.BundleActivator; > >>> import org.osgi.framework.BundleContext; > >>> > >>> public class Activator implements BundleActivator { > >>> private static final transient Log log = > >>> LogFactory.getLog(Activator.class > >>> .getName()); > >>> > >>> public void start(BundleContext context) throws Exception { > >>> log.info("EIBMappingService started"); > >>> } > >>> > >>> public void stop(BundleContext context) throws Exception { > >>> log.info("EIBMappingService stopped"); > >>> } > >>> } > >>> > >>>> Jean-Baptiste Onofre <[email protected]> hat am 21.08.2020 14:43 > >>>> geschrieben: > >>>> > >>>> > >>>> Hi Gerald, > >>>> > >>>> Do you have to wrap ? I guess it works with "regular" bundle, right ? > >>>> > >>>> Regards > >>>> JB > >>>> > >>>>> Le 21 août 2020 à 14:36, Gerald Kallas <[email protected]> a écrit : > >>>>> > >>>>> Dear all, > >>>>> > >>>>> I've a jar file that can be deployed with copying to the deploy folder. > >>>>> The log shows > >>>>> > >>>>> 2020-08-21T08:51:19,931 | INFO | > >>>>> fileinstall-/opt/apache-karaf-4.2.9/deploy | fileinstall > >>>>> | 10 - org.apache.felix.fileinstall - 3.6.6 | Installing bundle > >>>>> sfo-account-mapping / 0.0.1.SNAPSHOT > >>>>> 2020-08-21T08:51:20,105 | INFO | > >>>>> fileinstall-/opt/apache-karaf-4.2.9/deploy | fileinstall > >>>>> | 10 - org.apache.felix.fileinstall - 3.6.6 | Started bundle: > >>>>> wrap:file:/opt/apache-karaf-4.2.9/deploy/sfo-account-mapping-0.0.1-SNAPSHOT.jar$Bundle-SymbolicName=sfo-account-mapping&Bundle-Version=0.0.1.SNAPSHOT > >>>>> > >>>>> When I'm going to copy a new version of this jar the bundle is not > >>>>> being updated. > >>>>> > >>>>> I know this from Servicemix that even a new copy updates the bundle. Do > >>>>> I need to configure anything special in Karaf? > >>>>> > >>>>> Best > >>>>> Gerald
