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 solv
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 c
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 i
> 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
Hi
I am new to Maven , I have a problem about splitting a project into modules
and combining them into WAR.
I first build a parent project , naming 'destiny' with a POM (packaging
'pom') , and create 3 modules (sub-projects) :
1st is destiny-core (packaging : jar) : pure POJOs
2nd is destiny-weba
