| Summary: | The feature org.eclipse.jetty.all imposes 3rd party dependencies that make it difficult to use else where | ||
|---|---|---|---|
| Product: | [RT] Jetty | Reporter: | Hugues Malphettes <hmalphettes> |
| Component: | osgi | Assignee: | Hugues Malphettes <hmalphettes> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jetty-inbox |
| Version: | 7.3.0 | ||
| Target Milestone: | 7.3.x | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Hugues Malphettes
This type of question keeps coming back. The consensus is to be fairly conservative and actually impose versions of dependencies that are known to work; leaving less room to be able to plug a different set of dependencies. In this particular case, I will introduce a separate feature org.eclipse.jetty.all.dependencies It will carry all the dependencies avaialble on eclipse orbit and known to work with jetty-osgi. This feature will be included in the EclipseRTWebStarterKit. But this feature will not be included in org.eclipse.jetty.all Consumers of jetty-osgi will have the choice to define their own set of dependencies or to reuse jetty's org.eclipse.jetty.all.dependencies feature. Fixed for Indigo-M6: the dependencies are all placed in a separate feature which is not directly included in the RTWebStarterKit product. |