https://issues.apache.org/bugzilla/show_bug.cgi?id=43282
--- Comment #6 from Curt Arnold <[email protected]> 2010-06-12 01:33:17 EDT --- I've committed rev 953935 which results in a log4j.jar which can be installed and started in the Equinox OSGi framework supplied with Eclipse. For future ref: cd /usr/lib/eclipse/plugins java -jar org.eclipse.osgi_---.jar -console install file:///home/.../log4j-1.2.17-SNAPSHOT.jar start BUNDLE_FROM_PREVIOUS_STEP Based on a suggest from the 2008 exchange on u...@felix, I added a DynamicImport-Package directive via the maven-jar-plugin. Hopefully, that would allow resolving any user-supplied appender that was specified via a configuration file. javax.swing, com.ibm.uvm.tools and com.sun.jdmk.comm are explicitly blocked from being listed in the import list. Swing is used by the obsolete log viewing tools still in the java, but not exported. com.ibm.uvm.tools is dynamically loaded for some ancient VisualAge specific behavior. com.sun.jdmk.comm provides an http service for JMX. If needed, these classes can still be obtained via the DynamicImport-Package. I've listed three javax packages not included in Java SE 1.5 as optional. The javax.jmdns is not zeroconf implementation and despite the package name is not from Sun or part of the Java Community Process. All the other imported classes are either part of Java SE 1.5 or are exported by log4j.jar. The maven-bundle-plugin has enough info that it could provide the version qualifier on the exported classes, but it doesn't. I can bounce this off of us...@felix, but is there a reason that you think that we should specify it? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
