I don't think there is a general-purpose solution to the config combination problem. In some cases (log4j.properties, possibly ehcache.xml), the config file is, for the purpose of the jar modules, a test concern and thus can go in src/test/resources. BoxSpring (www.boxspring.org) is one way of solving this problem for Spring configuration files, i.e. tweaking Spring to support combining configuration.
Justin On 3/13/10 8:29 PM, smallufo wrote: > Wow , it works ! > But I have another question : > What if these modules share the same config files , such as log4j.properties > , or ehcache.xml , or spring's context.xml ? > Should I split one config file into different parts and put into > corresponding module ? (and if true , how to combine the parts into one ?) > Or what's the better way to manage these config files , so that each module > can locate it , and test separately it with problems ? > Thanks in advanced. > > > 2010/3/13 Wayne Fay <[email protected]> > >>> I need the three modules combined into one war , how to accomplish it ? >>> Thanks in advanced... >> >> Make a fourth project with "war" packaging, and depend on the other 3 >> projects, then run "mvn package" from the top/parent directory and >> eventually it will result in a war in the target folder of that 4th >> project. >> >> Wayne >> >> --------------------------------------------------------------------- >> 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]
