Azureus was using a FEW custom logging frameworks mixed in with some Log4J, which was really annoying when trying to separate the project into bundles. So what did I do, I moved it over to the JDK logging package. Took me all weekend but I am finished.

To make it OSGi-y I also wrote a package that implements a service that inserts itself as a handler into the JDK logging service and then passes those LogRecords onto the OSGi logging service, so that any bundle wanting to listen to the Torrent bundles logs can listen to either the JDK logger, or the OSGi Logger service.

Next is removing the custom plugin framework, and all the ad-hoc stuff that is implemented around it to make it modular.

All the internal stuff that goes on inside Azureus can be greatly simplified with the use of OSGi. But the process of moving is difficult, and the tools from going from legacy to OSGi code is arduous. Refactoring tools need to be developed to help this process.