Bugzilla – Full Text Bug Listing
| Summary: | The jetty source bundles are not available in the indigo repository | ||
|---|---|---|---|
| Product: | [RT] Jetty | Reporter: | Hugues Malphettes <hmalphettes> |
| Component: | osgi | Assignee: | Hugues Malphettes <hmalphettes> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | gunnar, jetty-inbox |
| Version: | 7.2.1 | ||
| Target Milestone: | 7.3.x | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Hugues Malphettes
Well, I unfortunately missed the M4 train but next contributed build will have the feature org.eclipse.jetty.bundles.f.source.feature.group which contains the sources of all the jetty bundles. Thanks Hugues. Assuming that Jetty 7.2 (7.x?) will be in Indigo, I was wondering if the Indigo repository should just point to the general 7.2.x releases repository instead of a separate repository? This way the Indigo build could pick up the latest available release. The 7.2.x repository contains only the jetty bundles in order to extract them from maven central, sign them and publish them in a p2-repo. In Indigo from our discussions with Jeff, we are publishing a more advanced packaging of those bundles: features suitable to create runtime servers and the Web StarterKit product and also the Jetty-SDK feature to provision target platforms for developers. At some point the eclipse-rt-packaging project will be consuming those features. That is why we are not contributing to indigo the jetty-bundles directly. BTW we are following with a lot of interest the improvements to the PDE launch that you are developing: really neat and better suited to developers than the SDK features where it is difficult to package configuration files and root IUs. Fixed in Indigo-M6 |