Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

On 17 Sep 2015, at 19:32, Gunnar Wagenknecht wrote: Am 16.09.2015 um 21:09 schrieb Joakim Erdfelt : What would this support layer be call in the Eclipse Equinox? Equinox does not provide such an implementation. However, if Jetty OSGi requires it to be present at runtime then there is like a

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

> Am 16.09.2015 um 21:09 schrieb Joakim Erdfelt : > What would this support layer be call in the Eclipse Equinox? Equinox does not provide such an implementation. However, if Jetty OSGi requires it to be present at runtime then there is like a CQ we could piggy-back for reuse. Thus, it shouldn't

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

On 09/17/2015 05:30 PM, Joakim Erdfelt wrote: the ServiceLoader requirement has existed since Jetty 8.0.x Its a fundamental feature of the Servlet 3.0 spec. If I understand correctly, the new requirement added with https://bugs.eclipse.org/bugs/show_bug.cgi?id=461919 is not the Service Loader p

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

the ServiceLoader requirement has existed since Jetty 8.0.x Its a fundamental feature of the Servlet 3.0 spec. On Thu, Sep 17, 2015 at 7:33 AM, Max Rydahl Andersen wrote: > > So Apache Aries is an extra dependency on the OSGi side to satisfy the >> various needs for ServiceLoader behavior in OS

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

So Apache Aries is an extra dependency on the OSGi side to satisfy the various needs for ServiceLoader behavior in OSGi, is that the case? There's many ServiceLoaders in a Servlet 3.1 Web Containers and even more with WebSockets. (the trend with Servlet 4.x discussions shows no sign of this a

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

So Apache Aries is an extra dependency on the OSGi side to satisfy the various needs for ServiceLoader behavior in OSGi, is that the case? There's many ServiceLoaders in a Servlet 3.1 Web Containers and even more with WebSockets. (the trend with Servlet 4.x discussions shows no sign of this abating

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

On 16 Sep 2015, at 17:04, Mickael Istria wrote: On 09/16/2015 04:54 PM, Joakim Erdfelt wrote: What does Apache Aries have to do with this? There's no references to Apache anything in the Jetty WebSocket layers in code nor in the manifests. Where is this reference / dependency coming from? Cer

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

On 09/16/2015 04:54 PM, Joakim Erdfelt wrote: What does Apache Aries have to do with this? There's no references to Apache anything in the Jetty WebSocket layers in code nor in the manifests. Where is this reference / dependency coming from? Certainly not Jetty. https://bugs.eclipse.org/bugs/s

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

On 09/16/2015 04:56 PM, Joakim Erdfelt wrote: Also a heads up. http://git.eclipse.org/c/jetty/org.eclipse.jetty.project.git/commit/?id=03a601f2b246a278961203a4b183100156d44dc1 The Jetty OSGi manifests will (in the next release/future) not resolve in large version ranges anymore. Great, than

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

Also a heads up. http://git.eclipse.org/c/jetty/org.eclipse.jetty.project.git/commit/?id=03a601f2b246a278961203a4b183100156d44dc1 The Jetty OSGi manifests will (in the next release/future) not resolve in large version ranges anymore. On Wed, Sep 16, 2015 at 7:45 AM, Mickael Istria wrote: > On

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

What does Apache Aries have to do with this? There's no references to Apache anything in the Jetty WebSocket layers in code nor in the manifests. Where is this reference / dependency coming from? Certainly not Jetty. On Wed, Sep 16, 2015 at 7:39 AM, Doug Schaefer wrote: > Can your code not depe

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

For the foreseeable future It will likely never be possible to mix Jetty websocket versions, the various specs (browser, main protocol, http/2 protocol, extensions, etc) are all changing rapidly STILL. On Wed, Sep 16, 2015 at 7:45 AM, Mickael Istria wrote: > On 09/16/2015 04:39 PM, Doug Schaefe

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

On 09/16/2015 04:45 PM, Mickael Istria wrote: On 09/16/2015 04:39 PM, Doug Schaefer wrote: Can your code not depend on an older version of jetty. Or is only one version of jetty allowed in a given bundle stack? Because of API inconsistencies, lack of conformance with semantic versioning and lax

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

On 09/16/2015 04:46 PM, Mickael Istria wrote: More precisely: Jetty won't complain, but there will be ClassNotFound at runtime. s/Jetty/p2/ More precisely: p2 won't complain, but there will be ClassNotFound at runtime. -- Mickael Istria Eclipse developer at JBoss, by Red Hat

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

On 09/16/2015 04:39 PM, Doug Schaefer wrote: Can your code not depend on an older version of jetty. Or is only one version of jetty allowed in a given bundle stack? Because of API inconsistencies, lack of conformance with semantic versioning and lax version ranges in Jetty bundles, it's not poss

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

Can your code not depend on an older version of jetty. Or is only one version of jetty allowed in a given bundle stack? Doug. On 2015-09-16, 4:50 AM, "cross-project-issues-dev-boun...@eclipse.org on behalf of Max Rydahl Andersen" wrote: >So jetty keeps on giving us some grief now and I think it

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

So jetty keeps on giving us some grief now and I think it is worth raising this since it has some nasty effects. If I had the option I would wish Jetty was reverted back to .9/.10 in Mars.1 until a more permanent/non-breaking option could be found, but I assume that is too late. Details below:

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

age >> 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

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

itor 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-proje

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

s 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 fee

Re: [cross-project-issues-dev] jetty versions - Another issue to feed on the topic of semantic versioning

nt: 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

[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 w