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_ka...@ca.ibm.com 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@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-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. | | From: | | -| |Alex Blewitt alex.blew...@gmail.com | -| | | To:| | -| |Equinox development mailing list equinox-dev@eclipse.org | -| | | Cc:| | -| |eclipse-...@eclipse.org eclipse-...@eclipse.org, cross-project-issues-...@eclipse.org cross-project-issues-...@eclipse.org, | |equinox-dev@eclipse.org equinox-dev@eclipse.org | -| | | 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_ka...@ca.ibm.com 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@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline: ecblank.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Update to Jetty and Servlet API in the M4 SDK
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: org.eclipse.equinox.http.jetty; bundle-version=[1.1,2.0) The Export-Package is still using 1.1 so Import-Package users should be fine. As a result of this change it is important for teams that are using the server-side bundles to verify as this change could cause problems. This is why the original email was sent and is a pre-step for an entry in the 3.4 to 3.5 migration guide. In most cases all should be well since the actual binary API has not changed although the bundle metadata has. -Simon | | From: | | --| |Alex Blewitt alex.blew...@gmail.com | --| | | To:| | --| |Equinox development mailing list equinox-dev@eclipse.org | --| | | Cc:| | --| |eclipse-...@eclipse.org eclipse-...@eclipse.org, cross-project-issues-...@eclipse.org cross-project-issues-...@eclipse.org, | |equinox-dev@eclipse.org equinox-dev@eclipse.org | --| | | Date: | | --| |12/11/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_ka...@ca.ibm.com 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@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline:
Re: [equinox-dev] Update to Jetty and Servlet API in the M4 SDK
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 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: org.eclipse.equinox.http.jetty; bundle- version=[1.1,2.0) The Export-Package is still using 1.1 so Import-Package users should be fine. As a result of this change it is important for teams that are using the server-side bundles to verify as this change could cause problems. This is why the original email was sent and is a pre-step for an entry in the 3.4 to 3.5 migration guide. In most cases all should be well since the actual binary API has not changed although the bundle metadata has. -Simon graycol.gifAlex Blewitt ---12/11/2008 02:50:38 PM---I thought that an API compatible change was only meant to increment ecblank.gif From: ecblank.gif Alex Blewitt alex.blew...@gmail.com ecblank.gif To: ecblank.gif Equinox development mailing list equinox-dev@eclipse.org ecblank.gif Cc: ecblank.gif eclipse-...@eclipse.org eclipse-...@eclipse.org, cross-project-issues-...@eclipse.org cross-project-issues-...@eclipse.org, equinox-dev@eclipse.org equinox-dev@eclipse.org ecblank.gif Date: ecblank.gif 12/11/2008 02:50 PM ecblank.gif Subject:ecblank.gif 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_ka...@ca.ibm.com 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@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
