Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337750 - [releng] Eclipse Helios SDK is missing the org.apache.lucene source bundle
Summary: [releng] Eclipse Helios SDK is missing the org.apache.lucene source bundle
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: 3.6.2+   Edit
Assignee: Kim Moir CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-21 13:15 EST by Martin Oberhuber CLA
Modified: 2011-02-21 13:52 EST (History)
2 users (show)

See Also:

Attachments
patch (1.71 KB, patch)
2011-02-21 13:30 EST, Kim Moir CLA 		no flags Details | Diff
View All 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 Martin Oberhuber CLA 2011-02-21 13:15:08 EST 
Build ID: Eclipse 3.6 - 3.6.2

The Eclipse Helios SDK is missing the org.apache.lucene_1.9.1.v20100518-1140 source bundle.

The source bundle is available from Orbit:
http://download.eclipse.org/tools/orbit/downloads/drops/R20100519200754/

So it should be shipped with the Eclipse SDK as well. This is important because adopters like us (Wind River) want to ship the full source of the Eclipse Platform along with our product, in order to comply with the common Open Source rule of having to provide source -- this is easiest when the source is shipped with the product.

I request fixing this for the Eclipse 3.6.2+ Maintenance Stream.

Note that in Eclipse 3.7 the problem has been addressed (source is being shipped for the newer Lucene 2.9.1 bundles).
Comment 1 Kim Moir CLA 2011-02-21 13:30:59 EST 
Created attachment 189433 [details]
patch
Comment 2 Kim Moir CLA 2011-02-21 13:32:11 EST 
Fixed.  I'm going to close this bug, since we don't have any 3.6.2+ builds scheduled.  I assume you'll be building the SDK yourself with this change.
Comment 3 Martin Oberhuber CLA 2011-02-21 13:44:26 EST 
Hm.... no M-builds after 3.6.2 ?

This is a problem for us, since we have no way getting any fixed plugins signed unless the builds occur at Eclipse. I guess I'm going to talk to the PMC about this on Wednesday.
Comment 4 Kim Moir CLA 2011-02-21 13:52:40 EST 
You can always request signing privileges from the webmasters. You can sign bundles manually via the command line, outside the build process.