Re: AW: Still integrating latest updates

Pierre,
>>
> I tested 3 possibilities with:
> - 1 = file test.xml in {KEEL_HOME}/app-personality/src/webapp/WEB-INF
> - 2 = file test.xml in {PROJECT_HOME}/src/webapp/WEB-INF
> - 3 = file test.xml in {PROJECT_HOME}/{MODULE}/src/webapp/WEB-INF
>
> then I got in {PROJECT_DIST}/WEB-INF the file test.xml:
> - 1 + 2 + 3 => from 3
> - 1 + 2       => from 1
> - 1 + 3       => from 3
>
> So the rule seems 3>1>2.
>
> I don't know if it's the expected rule. I think that 2>3>1 should be 
> clearer.
The order, as you found, makes sense.  2 is the "lowest priority" since 
it happens first, and then the other files just overwrite it.  The 
reason it happens first is that "keel:webapp" is invoked in a "postGoal" 
to Maven's "war:webapp".  "war:webapp" copies {PROJECT_HOME}/src/webapp 
files, and then the "keel-webapp" moves files from the other JARs.  The 
priority between 1 & 3 are based simply in the ordering of "dependency" 
elements in the project.xml, the ones lower in the file will end up 
overwriting others.

I too think 2>3>1 makes sense.  To do that, we should suggest in the 
example project.xml(s) that the users own modules should be after the 
Keel modules (this gets 3>1).  To get 2>3, we can experiment with making 
the postGoal a preGoal, or copying the {PROJECT_HOME}/src/webapp files a 
second time at the end of keel:webapp.

Shash