Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362217 - Stop building org.eclipse.equinox.http
Summary: Stop building org.eclipse.equinox.http
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 3.8   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 3.8 M4   Edit
Assignee: Kim Moir CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 362724
  Show dependency tree
 
Reported: 2011-10-27 12:29 EDT by Thomas Watson CLA
Modified: 2011-11-10 18:51 EST (History)
7 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Watson CLA 2011-10-27 12:29:11 EDT 
As we move to supporting servlet 3.0 I think we should stop building the old (non-jetty based) HttpService implementation and stop shipping it with the SDK for 3.8.
Comment 1 Thomas Watson CLA 2011-10-27 14:16:42 EDT 
(In reply to comment #0)
> As we move to supporting servlet 3.0 I think we should stop building the old
> (non-jetty based) HttpService implementation and stop shipping it with the SDK
> for 3.8.

To be clear I am talking about the Equinox SDK, NOT the Eclipse SDK.  We have never shipped this bundle in the Eclipse SDK.
Comment 2 Alex Blewitt CLA 2011-10-27 14:44:15 EDT 
Is there any reason not to ship it in the Eclipse SDK as well as the Equinox SDK? Or, for that matter, finally moving forward and using the Eclipse-built Jetty instead of the old org.mortbay one?
Comment 3 Alex Blewitt CLA 2011-10-27 14:45:42 EDT 
See e.g. https://bugs.eclipse.org/bugs/show_bug.cgi?id=271042
Comment 4 Thomas Watson CLA 2011-10-27 14:58:28 EDT 
(In reply to comment #2)
> Is there any reason not to ship it in the Eclipse SDK as well as the Equinox
> SDK? Or, for that matter, finally moving forward and using the Eclipse-built
> Jetty instead of the old org.mortbay one?

In the move to support servlet 3.0 we are moving to jetty 8 which is Eclipse-Built.  See bug309529.  The desire to move to jetty 8 and servlet 3.0 is what has prompted me to ask this question.  We could keep building the old http service impl and try to deal with the headaches of using two versions of the javax.servlet packages.  Or we can simply move on and stop building the old stuff that, to be honest, is not really maintained by any active committers.

If folks really still need to old http service impl then they can go to one of our previous releases and get the bundles.  But I don't see any need to keep building this old implementation any more.

For that matter I think we should stop building the old jetty5 and jetty6 based http service implementations also.  No need to keep pulling in the old mortbay jetty bundles for things we no longer use or maintain.
Comment 5 Simon Archer CLA 2011-11-07 17:05:24 EST 
Also see bug 363105, "Stop building jetty5, jetty6 and org.mortbay.jetty.* bundles".
Comment 6 Kim Moir CLA 2011-11-10 16:22:16 EST 
Tom, can you please remove 

generate.plugin@org.eclipse.equinox.http.source=org.eclipse.equinox.http

from the build.properties of the equinox.serverside.sdk feature

My commit rights are still not working on that repo.
Comment 7 Kim Moir CLA 2011-11-10 16:52:50 EST 
regarding comment #6, 

I got DJ to make the change.
Comment 8 Kim Moir CLA 2011-11-10 18:51:18 EST 
Fixed for N20111110-2000.