2009/8/21 Cornelius, Martin (DWBI) <[email protected]>
> > I'm just getting started to 'osgify' a large application that uses > several external libraries, e.g. log4j. Thus, i first have to get > 'bundelized' versions of all these jars to deploy them to my felix > runtime. > > I already learned that it's possible to 'bundelize' existing jars using > the Bnd utility. However, googling around i found a felix jira entry > stating that log4j has already been bundelized by the felix project > developers, see: > https://issues.apache.org/jira/browse/FELIX-230 > > However, i could not find this bundle on the felix download site, nor in > the official felix bundle repository. Does this mean that i have to > build the bundle myself from the sources ? If true, how do i do that ? > the code is in svn, but has not had a formal release (and afaik it is unlikely to be released) http://svn.apache.org/repos/asf/felix/trunk/commons/log4j you can build it yourself, but you might prefer to use an alternative such as pax-logging: http://wiki.ops4j.org/display/paxlogging or the Apache Sling logging bundle: http://sling.apache.org/site/logging.html both provide the Log4j API (and other logging APIs) while using a single backend logger finally the Spring Bundle Repository has a number of bundle-ized libraries for Log4J: http://www.springsource.com/repository/app/search?query=log4j but these are mostly the original jars with OSGi metadata, whereas the Sling and Pax bundles have been optimized for OSGi and support the OSGi framework LogService HTH Thanks for any hints, Martin > > ************************************************ > The information contained in, or attached to, this e-mail, may contain > confidential information and is intended solely for the use of the > individual or entity to whom they are addressed and may be subject to legal > privilege. If you have received this e-mail in error you should notify the > sender immediately by reply e-mail, delete the message from your system and > notify your system manager. Please do not copy it for any purpose, or > disclose its contents to any other person. The views or opinions presented > in this e-mail are solely those of the author and do not necessarily > represent those of the company. The recipient should check this e-mail and > any attachments for the presence of viruses. The company accepts no > liability for any damage caused, directly or indirectly, by any virus > transmitted in this email. > ************************************************ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cheers, Stuart
