| Summary: | Create source bundles and feature | ||
|---|---|---|---|
| Product: | [Tools] Objectteams | Reporter: | Stephan Herrmann <stephan.herrmann> |
| Component: | Releng | Assignee: | Project Inbox <objectteams.releng-inbox> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | Keywords: | noteworthy |
| Version: | 2.1 | ||
| Target Milestone: | 2.1 M6 | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Stephan Herrmann
We need this before EclipseCon! After a series of trial-and-error this has been resolved for 2.1M6. What doesn't work: - Just specifying generate.feature@... in the OTDT feature produced absolutely no result (nor an error message) - generating a source feature with the same name as the branding plugin (org.eclipse.objectteams.otdt.source) produced no source plugin for the branding plugin (nor an error message) What works: - Manually defining a source feature (with feature.xml and all) and explicitly listing all included source plugins both in feature.xml *and* build.properties. While working on these changes I wondered whether our custom OTDT build interferes with some of PDEBuild's black magic. Maybe we should split the OTDT-Build step into OTDT-Build and OT-Test steps, maybe then we can discard our customizations and use a standard build. Verified at 2.2 M3. |