[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[eclipse-dev] Re: [equinox-dev] Update to Jetty and Servlet API in the M4 SDK
|
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.
Alex Blewitt ---11/12/2008 02:50:38 PM---I thought that an API compatible change was only meant to increment the minor version number, rath
From: |
Alex Blewitt <alex.blewitt@xxxxxxxxx> |
To: |
Equinox development mailing list <equinox-dev@xxxxxxxxxxx> |
Cc: |
"eclipse-dev@xxxxxxxxxxx" <eclipse-dev@xxxxxxxxxxx>, "cross-project-issues-dev@xxxxxxxxxxx" <cross-project-issues-dev@xxxxxxxxxxx>, "equinox-dev@xxxxxxxxxxx" <equinox-dev@xxxxxxxxxxx> |
Date: |
11/12/2008 02:50 PM |
Subject: |
Re: [equinox-dev] Update to Jetty and Servlet API in the M4 SDK |
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_Kaegi@xxxxxxxxxx> wrote:
> 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 appropriate bundles from
> Orbit yourself.
>
> 2) org.mortbay.jetty.server and org.mortbay.jetty.util (version 6.1)
> (added)
>
> 3) javax.servlet (upgraded from version 2.4 to 2.5)
> API compatible. Bundle-Version and Export-Package version updated.
> Teams should verify version ranges for Import-Package and Require-
> Bundle.
>
> 4) org.eclipse.equinox.http.jetty (upgraded from version 1.1 to 2.0)
> API compatible. Bundle Version updated but no change to Export-
> Package version. Teams using Require-Bundle with a restricted bundle-
> version range should confirm.
>
> --
> None of these changes introduce new Eclipse binary API or prevent
> the use of existing API.
>
> If anyone has a problem please log a bug against RT->Equinox->Server-
> Side
>
> -Simon
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev