Community
Participate
Working Groups
Glyn observed that it is awkward to mark the jetty.osgi.boot bundle with the lazy activation policy. web-bundles would have a harder time to decide that jetty.osgi.boot is started and will indeed deploy the webapp just because one of its classes is loaded.
For our own projects we usually auto-start jetty fairly early and web-bundles are started later which is the less dynamic scenario and the one that creates th least surprises: we don't depend on jetty.osgi.boot lazy activation either and in fact no one should load classes from jetty.osgi.boot. Committed revision 2471 Fixed for 7.2.1
Will this fix appear on the 7.x line as it's not in the latest 7.2.2.v20101205. Just wondering if we will have to wait for 8 to release? Thanks for your help. Chris.
Hi Chris, in theory it is committed and released already. If there is something missing all the fixes are going into the up-coming 7.2.3 and in the future 8.0 releases too. I am finally catching up with the jetty-bugs. Tomorrow onto the jsp tag libs and releasing all this.
I'm a little excited then, will the tag libs feature make it in to 7.2.3 as well. If so might have a fully functional Virgo + Jetty server soon. Just to make sure, when your on it tomorrow could you double check the lazy activation for osgi-boot has gone. Would be appreciated. Thanks for everything, Chris.
The 7.3 release still has the org.jetty.osgi.boot bundle with the lazy activation policy bundle set.
Bummer: although the MANIFEST.MF was corrected the Bundle-Activation policy was still specified in the pom.xml. Sorry this escaped me. Fixed with commit 2768 Chris I can try to upload a patched 7.3.0 somewhere if it helps.
Hi, It's OK, I've made the change locally and that will do for now. I assume there will be another release on the 7.x.x line. If so I can wait for that as it's not urgent. Chris.
Ok cheers Chris, my apologies on missing this. New motto for me: "The smaller the change the more weary you should be be".
7.3.1 ought to be out in a couple of weeks
