Re: Best practices for avoiding duplicate configuration files

2009-04-29 Thread Olivier Cailloux
Ceki Gulcu a écrit : Olivier, Since projects A and B seem to be just artifacts, I am still wondering why projects A and B need a configuration file for logging. If it is for testing purposes, why not use logback-text.xml and place it under /src/test/resources/ directory? Indeed, it appears to me

Re: Best practices for avoiding duplicate configuration files

2009-04-29 Thread Olivier Cailloux
ogging framework!). Also, sorry for my English... Olivier Brian Fox a écrit : See the 9th bullet point here: http://www.sonatype.com/people/2009/04/summary-of-maven-how-tos/ On 4/26/2009 3:17 PM, Olivier Cailloux wrote: Hello list, I am new to maven and couldn't find a simpl

Re: Best practices for avoiding duplicate configuration files

2009-04-27 Thread Olivier Cailloux
se logging framework!). Also, sorry for my English... Olivier Brian Fox a écrit : See the 9th bullet point here: http://www.sonatype.com/people/2009/04/summary-of-maven-how-tos/ On 4/26/2009 3:17 PM, Olivier Cailloux wrote: Hello list, I am new to maven and couldn't find a simple and eleg

Best practices for avoiding duplicate configuration files

2009-04-27 Thread Olivier Cailloux
Hello list, I am new to maven and couldn't find a simple and elegant solution to this (probably) common problem. I have three projects : A and B are independent projects and C depends on A and B. I use the same logging framework for the three projects (slf4j with logback). In A and B, I have