On Dec 4, 2007 3:40 AM, heimlich <[EMAIL PROTECTED]> wrote: > The problem is that each subproject tries to refer to the 'filters' > directory IN ITS OWN directory structure, > not the one at the top. > > The reason for this structure is that I want: > > ONE conf.properties > ONE filter file per profile > > and I want the filtered conf.properties copied into src/main/resources of > each subproject > (I'm, willing to consider having copies of an unfiltered conf.properties in > each project's resources directory). > Can it be done (how?) or should try a different approach (any suggestions)? ... > Or should I have no filtering, and just three different properties files > (dev, test and prod) > at the top and have them included in each concrete project (how do I do > that)?
You could put the files in a separate module, build a jar from them, and dependency:unpack them into each one. Or just list that jar as a dependency, if the calling code can find files on the classpath. Something else to consider is whether you are re-building your project for each environment, potentially introducing changes _after_ it has been tested. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
