Sorry for the misnomer, but the bundles between them self seem to have used It as Api.
And yes we know by heavy experience that mixed versions of Jetty is bad - even at the .z level. We've had the issue in past - it's just that it now repeated and thus we wanted to raise it to know how to handle it. But there is now way for us to actually control this when jetty itself in its version ranges says .10 when it actually needs .13 and vice Versa. I.e. Platform required some jetty .9 or upwards at Mars.0, We add a dependency in our plugins to other parts of jetty as .9 and upwards. As long as only .9 is available to Osgi to resolve things are good. In Mars .1 jetty .13 is bundled. Now when our bundles are resolved it ends up with a mix of .9 and .13 with no dependency resolution errors. Only at runtime the issue occurs since .9 and .13 are actually *not* compatible with each other. /max http://about.me/maxandersen > On 15 Sep 2015, at 03:02, Joakim Erdfelt <joakim.erdf...@gmail.com> wrote: > > We monitor this list. > > However, the filed bug says "This class was API and was used by several of > the other jetty bundles." > Which is confusing, as SpinLock is internal, not API. > And using mixed versions of Jetty (on the server side) is generally frowned > upon (at least from the non-OSGi point of view). > > >> On Mon, Sep 14, 2015 at 2:16 PM, Mike Milinkovich >> <mike.milinkov...@eclipse.org> wrote: >> >> Just out of curiousity, have you asked on the Jetty dev list? Since they're >> only on the release train indirectly, I'm not sure how well they monitor >> this list? >> >> >> Mike Milinkovich >> mike.milinkov...@eclipse.org >> +1.613.220.3223 >> Original Message >> From: Max Rydahl Andersen >> Sent: Monday, September 14, 2015 10:15 PM >> To: cross-project-issues-dev@eclipse.org >> Reply To: Cross project issues >> Subject: [cross-project-issues-dev] jetty versions - Another issue to feed >> on the topic of semantic versioning >> >> I don't want to hijack the other thread, but it is related. >> >> JBoss Tools noticed that Jetty has some funky API changes going >> on which unless you are super careful things breaks. >> >> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=477385 >> >> basically jetty 9.2.9, 9.2.10 and 9.2.13 are not compatible with/between >> each other. >> >> Resulting in if platform ships some parts of jetty 9.2.13 and your >> manifest says it works with 9.2.10 (jetty owns libraries says it does) >> then things fall apart since you end up with a mix of 9.2.10 and 9.2.13 >> in your install and that just don't work. >> >> Just wondering if others seen this and/or got any tips to better fix >> this going forward (besides restricting ones version range to 9.2.10 and >> nothing else) >> >> /max >> http://about.me/maxandersen >> _______________________________________________ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> _______________________________________________ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
