Why don't you just create a submodule only containing that logging configuration (and possible other shared classpath resources) and make it a dependency of all the other modules? That's what we do.
Kalle On Sun, Sep 27, 2009 at 6:27 PM, Paul Benedict <[email protected]> wrote: > Brian, it just sounds awfully complex. A simple matter such as sharing a > log4j.property at the root of a nested project shouldn't create so much > work. Any other avenue? I am glad you shared this information. > > Paul > > On Sat, Sep 26, 2009 at 10:12 PM, Brian Fox <[email protected]> wrote: > >> Something like this approach should work: >> >> http://www.sonatype.com/people/2008/04/how-to-share-resources-across-projects-in-maven/ >> >> On Sat, Sep 26, 2009 at 7:37 PM, Paul Benedict <[email protected]> >> wrote: >> > I find myself replicating the same log4j configuration in my Maven >> projects. >> > It's a typical setup I want my projects to always use. Is there any good >> way >> > to specify one in a parent POM for all child projects? Would the >> > maven-remote-resources-plugin be useful for this? >> > >> > Paul >> > >> >> --------------------------------------------------------------------- >> 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]
