pax-logging-api exports the org.apache.log4j.spi package but LoggingEvent class placed at pax-logging-service and cause
Workaround is to use
but LoggingEvent class is expected to be visible at runtime
What's your use case exactly ?
If you're implementing a custom appender or something like that, the usual way to do that is to attach your code as an OSGi fragment to the pax-logging-service bundle. In such a case, the class will be visible to your code.
Bundle reads org.apache.log4j.spi.LoggingEvent from external source; logic is not related to pax-logging-service at all
Now, after changes related to PAXLOGGING-252, all "API" packages are actually exported from pax-logging-api: