Use one logging file with variable values, in conjunction with filters and profiles.
The "Better Builds with Maven" book should help you understand how to set this up in sections 2.6.2 and 3.8. Its not hard, but neither is it trivial, so I'm not going to really go into an example here over email... Wayne On 5/11/06, Davis Ford <[EMAIL PROTECTED]> wrote:
Hi, I was wondering if someone might be able to describe how to solve the following problem: We have one master project pom.xml that has <module></module> in it. A team can check out a <module> that has its own pom.xml and build it independently. At the end of the day, the master pom.xml builds all subprojects and runs integration tests. There is one subproject called logging that controls logging for the project using log4j. It has a logging.xml file as a resource. However, each developer will want to tweak the logging.xml file to his/her tastes while developing. What I would like to do is set the logging.xml file as a resource of the master project, and then have the logging subproject use that file (if it exists), or if it does not exist, default to its own logging.xml resource file. This would allow a developer to edit the master project logging.xml for their local builds, and have the logging.jar reference that. How can I accomplish this in mvn, or is there a better way to achieve the end goal? Thx, Davis --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
