Apache Log4J

With log4j it is possible to enable logging at runtime without modifying the application binary. The log4j package is designed so that these statements can remain in shipped code without incurring a heavy performance cost. Logging behavior can be controlled by editing a configuration file, without touching the application binary. Logging equips the developer with detailed context for application failures. On the other hand, testing provides quality assurance and confidence in the application. Logging and testing should not be confused. They are complementary. When logging is wisely used, it can prove to be an essential tool. One of the distinctive features of log4j is the notion of inheritance in loggers. Using a logger hierarchy it is possible to control which log statements are output at arbitrarily fine granularity but also great ease. This helps reduce the volume of logged output and minimize the cost of logging.

http://logging.apache.org/log4j/

• HELENOS - KDD Workbench
• Hydra - Software Property Manager
• RDF Reactor
• Wiki Interchange Format
• Metis - FocusedCrawler
• Almo - A workflow engine
• semweb4j
• rdf2go
• SemVersion - RDF Versioning