In M4 the platform team updated the version of Jetty that comes packaged
with the SDK from 5.1 to 6.1.
This impacts the following bundles:
1) org.mortbay.jetty (version 5.1) (removed)
If your feature directly integrates with the Jetty 5 API you can continue
to do so but must now add the
I thought that an API compatible change was only meant to increment
the minor version number, rather than the major number?
Alex
Sent from my (new) iPhone
On 11 Dec 2008, at 19:02, Simon Kaegi simon_ka...@ca.ibm.com wrote:
In M4 the platform team updated the version of Jetty that comes
The Jetty team does not use the eclipse convention to version their code.
Despite this difference we prefer to reuse their version number rather than
coming up with one.
|
| From: |
|
Yes you're right.
The bundle-version on org.eclipse.equinox.http.jetty is bumped to 2.0 so
to high-light Alex's point/concern...
There is the possibility of breakage if a team used a version restricted
Require-Bundle with major version semantics like:
Require-Bundle:
So the question is ... Why are you bumping o.e.e.h.jetty from 1.1-2.0
instead of 1.1-1.2?
Sent from my (new) iPhone
On 11 Dec 2008, at 20:59, Simon Kaegi simon_ka...@ca.ibm.com wrote:
Yes you're right.
The bundle-version on org.eclipse.equinox.http.jetty is bumped to
2.0 so to high-light
