Bugzilla – Full Text Bug Listing
| Summary: | [releng] DLTK should create/package individual source bundles | ||
|---|---|---|---|
| Product: | [Technology] DLTK | Reporter: | Martin Oberhuber <mober.at+eclipse> |
| Component: | Common | Assignee: | dltk.common-inbox <dltk.common-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | andrei.sobolev, andrey, zulus |
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Ping, could this be considered ? Yes, Martin, sure. Is this a must do for Indigo SR? I'm asking because relevant guys are on vacation now, so trying to understand if we have to assign someone else to repackage features. It's not a must-have, but the change should be simple enough (1-liner in build.properties, no change to any features needed):
individualSourceBundles=true
Anybody who can build DLTK should be able to apply the change easily.
The change should probably go into releng.dltkbuilder/build.properties, but I'm a little confused since the dltkbuilder hasn't changed since 2008 and it looks like the version of the basebuilder being used might be too old (eclipse.builder.version=RC4_33 --> Eclipse 3.3 wouldn't understand the new property).
Ping, is any releng person back from vacation to give this a try? Again the change should be a one-liner, and would definitely help our adoption. Hi Martin, I've checked our current build environment and found what we are still using Eclipse 3.3 based pde builder, and there is not support for individualSourceBundles. Right now we are moving to Maven/Tycho, so we will provide individual source bundles support in new environment, instead of modifying existing one. We plan to move to maven/tycho before Juno M2 release. Thanks, Andrei Ping, how is the move to Maven / Tycho going ? (In reply to comment #6) > Ping, how is the move to Maven / Tycho going ? Hi Martin, We have tycho 0.12 based builds available at: http://download.eclipse.org/technology/dltk/updates-dev/4.0-nightly/ And in our download area: http://download.eclipse.org/technology/dltk/downloads/drops/R4.0/I-I201111171055-201111171055/ We still yet not provide it into Juno, because of not finished signing process. Best regards, Andrei Sobolev. Ping, any progress on DLTK builds ? FYI, adopting Tycho-0.13 as builder may be important for Juno since it comes with the newer (Juno based) p2 publisher which treats optional dependencies the way it's expected for Juno. See also recent postings on the cross-project mailing list. Hi Martin, DLTK builds right now are in Tycho 0.12, and included in Juno aggregations. Build could be obtained from here: https://hudson.eclipse.org/hudson/job/dltk-nightly/ I will check for Tycho 0.13, and comment. It should not be a problem to use 0.13. Marking as fixed. DLTK it's now on Tycho 0.23, each feature have corresponding SDK feature with source bundles. |
DLTK ships its sources the "old style way" with a single source bundle for the entire feature. This is problematic for an adopter who only needs parts of the feature - individual source bundles should be created instead. When using PDE Build, then usually this is as simple as setting the following property in the master build.properties file: individualSourceBundles=true For even better build consumability, the following properties should be considered too: generateFeatureVersionSuffix=true generateAPIDescription=true generateSourceReferences=true