L.S., This sounds like a pretty important issue to me - wouldn't that impact anybody's who tries to run ServiceMix whenever the container gets restarted? Not sure if it is possible at the moment off course, but wouldn't it be better to at least do a new minor fileinstall + karaf release so we can tell people that run into this problem to switch to equinox - as soon as felix releases a new version of the framework, we can then upgrade that again.
Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ 2009/12/15 Chris Custine <[email protected]>: > Without the fix, many of the example projects (or any other bundles that > import packages from a startlevel 60 bundle) will fail to resolve on restart > if you originally deployed using fileinstall. The reason is that some > recent changes to fileinstall cause it to start its managed bundles when > fileinstall starts, which is startlevel 11. > > The fix to fileinstall works with Equinox, but it uncovered a bug in Felix > framework bundle (https://issues.apache.org/jira/browse/FELIX-1929). Until > framework bundle is released with the fix, the only solution in Felix is to > refresh the fileinstall managed bundles after startlevel 60 bundles are > resolved. Another alternative is to switch to Equinox. > > If we don't release fileinstall with this fix, the only option for both > Equinox and Felix is the refresh option. I'm OK with releasing either way, > I just wanted to make sure everyone understood the issue before we go ahead. > > Chris > > -- > Chris Custine > FUSESource :: http://fusesource.com > My Blog :: http://blog.organicelement.com > Apache ServiceMix :: http://servicemix.apache.org > Apache Directory Server :: http://directory.apache.org > > > On Tue, Dec 15, 2009 at 10:57 AM, Guillaume Nodet <[email protected]> wrote: > >> I don't think we should wait on this fix. It would also require a >> release of felix framework because Chris' patch raised a buf in the >> framework. >> What kind of problems would our users run into if we release without the >> fix ? >> >> On Tue, Dec 15, 2009 at 18:14, Gert Vanthienen >> <[email protected]> wrote: >> > L.S., >> > >> > For the SMX 4.1 release, I think we have a problem with >> > https://issues.apache.org/jira/browse/FELIX-1928. This issue in >> > FileInstall has been fixed after the Karaf 1.2.0 release had been cut, >> > but it could have quite a bit of impact on our users. It might make >> > more sense to work towards a new release of FileInstall and Karaf >> > first before cutting the SMX 4.1 release, but any suggestions or ideas >> > are welcome. >> > >> > For the plugins/components, we can still go ahead and release those. >> > I can release those tomorrow - I have a few hours available to cut the >> > release tomorrow afternoon, unless anyone knows about outstanding >> > issues that need to go into the release before we can go ahead. >> > >> > Regards, >> > >> > Gert Vanthienen >> > ------------------------ >> > Open Source SOA: http://fusesource.com >> > Blog: http://gertvanthienen.blogspot.com/ >> > >> > >> > >> > 2009/12/14 Jean-Baptiste Onofre <[email protected]>: >> >> Gert, >> >> >> >> it makes sense yes :) >> >> >> >> I begin the process. >> >> >> >> Regards >> >> JB >> >> >> >> Gert Vanthienen wrote: >> >>> >> >>> Jean-Baptiste, >> >>> >> >>> How about doing a big, bulky 4.1 release this week with components + >> >>> nmr + features in it and then follow up with a servicemix 3.3.2 >> >>> release next week, reusing the same component set? That way, we can >> >>> announce a new release both weeks ;) >> >>> >> >>> Regards, >> >>> >> >>> Gert Vanthienen >> >>> ------------------------ >> >>> Open Source SOA: http://fusesource.com >> >>> Blog: http://gertvanthienen.blogspot.com/ >> >>> >> >>> >> >>> >> >>> 2009/12/14 Jean-Baptiste Onofre <[email protected]>: >> >>>> >> >>>> Hi gentlemen, >> >>>> >> >>>> Yesterday I have upgraded SMX resources (component, feature, etc) to >> use >> >>>> Apache Camel 2.1 as it has been released. >> >>>> >> >>>> I think that we are not so far from a new SMX 3.3.2 and 4.1 release. >> >>>> >> >>>> I propose the following steps: >> >>>> >> >>>> 1/ I begin to prepare the 2009.02 components release. It includes: >> >>>> - component-pom 4 >> >>>> - jbi-maven-plugin 4.2 >> >>>> These artifacts will be submit to a first vote. >> >>>> - all components 2009.02 >> >>>> All components artifacts will be submit to a second vote. >> >>>> >> >>>> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly >> using >> >>>> Karaf 1.2.0 and perform some test to check how it runs. >> >>>> >> >>>> 2/ once these steps 1 and 1 bis have been performed, we can upgrade >> the >> >>>> smx >> >>>> 3 and smx 4 POMs to use the previously released components. >> >>>> Two votes will be submitted: one for SMX3 and another one for SMX4. >> >>>> >> >>>> What do you think about that ? >> >>>> >> >>>> Regards >> >>>> JB >> >>>> >> >> >> >> -- >> >> Jean-Baptiste Onofré >> >> --------------------------------- >> >> HomePage >> >> http://www.nanthrax.net >> >> --------------------------------- >> >> Contacts >> >> [email protected] >> >> [email protected] >> >> --------------------------------- >> >> OpenSource >> >> BuildProcess/AutoDeploy >> >> http://buildprocess.sourceforge.net >> >> Apache ServiceMix >> >> http://servicemix.apache.org >> >> ----------------------------------- >> >> PGP : 17D4F086 >> >> >> > >> >> >> >> -- >> Cheers, >> Guillaume Nodet >> ------------------------ >> Blog: http://gnodet.blogspot.com/ >> ------------------------ >> Open Source SOA >> http://fusesource.com >> >
