Bug #26
clarify classpath usage for some bundles jar dependencies
| Status: | Feedback | Start: | 10/19/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | Infrastructure | |||
| Target version: | 0.5.4 |
Description
Some jars (like the logging stuff) are brought into the runtime by means of being included with the Weaver.jar pseudo-bundle (its not a true bundle bc. it is loaded upfront and is equinox specific).
This means that they have a runtime-dependency to thos jars that is resolved by the Weavers build-process, which I consider 'bad'.
There needs to be a runtime-reference to those jars or the need to be packed into a separate bundle or whatever.
History
Updated by Philipp Haußleiter about 2 years ago
- Status changed from New to Feedback
- Target version set to 0.5.4
All osgi jars are now consolidated within the framework.
Logging and Weaving has still to be cleaned.