I'm setting up a template project for future all of our future projects to begin with...kind of a starting point that already has the tools necessary for our development architecture. I just realized that I have never had to set up Log4j in an enterprise project...it's always just "been there". I don't think I'll have difficulty with the build script building out the project. However, when it comes to setting up a tool like Log4j that will be used in java projects as well as web projects and potentially EJB projects, I don't really know where to store the Log4j.jar & Log4j.xml file so I that I don't have them laying around in every project. I am interested in the best practices strategy for tools that are shared among projects tied to an EAR project and any information you all think might be useful.
Joined: Sep 05, 2009
One clarification to make clearer what I'm looking for...
I want to move to more of an enterprise approach. I am not looking to just dump a jar file in the web's lib directory & the xml file into the classpath of the build. I want to be able to treat the xml file as a resource and have the ability to manipulate it without recompiling and I'd like to avoid classloading issues by referring to a common version of the jar file. As I said, any advise you can give or information you can point me to would be much appreciated...
Peter, good advise...I was headed in that direction but our decision has not been made to use Maven so I was waiting on that while still experimenting with some of our tools. Do you have any advise if the other groups decided against Maven?
subject: Log4j / Eclipse strategy for Enterprise application