[LOG4J2-515] Support OSGi bundles without requiring OSGi dependencies.

• Type: Epic
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-rc1
• Fix Version/s: 3.0.0
• Component/s: API, Appenders, Configurators, Core, Filters, Layouts, Receivers
• Labels: bundle osgi

Environment

OSGi, non-OSGi

• Epic Name: OSGi Support
• Assignee: Unassigned
• Reporter: Matt Sicker
• Created: 26/Jan/14 23:46
• Updated: 01/Dec/23 23:48
• Resolved: 01/Dec/23 23:48

Description

In order to properly support OSGi, we need to use a combination of ideas.

1. Packages and modules should be as coherent as possible. This makes bundling them into bundles and services significantly easier. Plus, it's a good idea anyway.
2. Use Felix SCR annotations in order to support more advanced OSGi concepts without requiring an explicit dependency on OSGi. This way, the annotations can be discarded or ignored by non-OSGi environments.
3. Provide more bundles. The core bundles, while a good start, could be further modularized.
4. Don't rely on class loader hacks. Instead, methods that need to use a class loader should always include a ClassLoader parameter. Class loader hacks can be used in centralized locations as a fallback mechanism where no advanced class loaders are provided.