• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Log4j / Eclipse strategy for Enterprise application

 
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.

Thanks,
Travis
 
Travis Prescott
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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...
 
author
Posts: 5856
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You might want to look into Maven, it already provides much of what you are asking.
 
Travis Prescott
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?

Thanks,
Travis
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic