The Artima Developer Community
Sponsored Link

Java Buzz Forum
Log4E: Eclipse plugin for Log4J. Does a great job of anti-AOP :)

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
dion

Posts: 5028
Nickname: dion
Registered: Feb, 2003

Dion Almaer is the Editor-in-Chief for TheServerSide.com, and is an enterprise Java evangelist
Log4E: Eclipse plugin for Log4J. Does a great job of anti-AOP :) Posted: Jul 26, 2004 11:09 AM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by dion.
Original Post: Log4E: Eclipse plugin for Log4J. Does a great job of anti-AOP :)
Feed Title: techno.blog(Dion)
Feed URL: http://feeds.feedburner.com/dion
Feed Description: blogging about life the universe and everything tech
Latest Java Buzz Posts
Latest Java Buzz Posts by dion
Latest Posts From techno.blog(Dion)

Advertisement
Log4E is a free Eclipse Plugin which helps you to use your logger easily in Java Projects. One of the nice features is that you can grab a project that has a bunch of System.out.println()'s and you can convert them to using a real Log system. One of the scary things is: Automatic inserts of logger statements at certain method entries: begin of method, exit of method (before every return statement and at the end of method) and in catch blocks. Although tools like Eclipse, IntelliJ IDEA, etc are great for helping get stuff in. This doesn't mean that they are good at going the other way. What I mean here is that a lot of these great tools help with complexity one way. I have heard a lot of people say "It is so easy to do X in my IDE, it doesn't matter than the result is a bunch of code". What happens when you have to come BACK to the code to understand it? It may have been easy to say "I want a new [insert design pattern here]" and have interfaces, base impls, DTOs, XML config, etc generated at once. However we have to grok this at a later date. This is why it I would rather look at simpler, smaller code!

Read: Log4E: Eclipse plugin for Log4J. Does a great job of anti-AOP :)

Topic: High-level Java AIM/OSCAR API to be released Previous Topic   Next Topic Topic: Jakarta Struts De-Mystified Part 2

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use