jerome lacoste wrote:

>On 10/22/05, Brett Porter <[EMAIL PROTECTED]> wrote:
>  
>
>>If they are never used independantly I'd say merge, otherwise I'd say
>>fix the war plugin, merge the 2 web.xml's, and add that as the
>>resulting one.
>>    
>>
>
>OK.
>
>My idea is that there shouldn't be any merging of xml files to do.
>
>The war would just automatically use the WEB-INF as found locally. For
>that I think the plexus WarAchiver needs to be passed the 'update'
>argument, and I need to find out how this can be done.
>
>See http://jira.codehaus.org/browse/MNG-1274.
>
>Cheers,
>
>Jerome
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>  
>
switching to thing thread from my previous email titled "maven2:
repackage/merge war's".

my use case is this:

Suppose I have a maven project with packaging set to war and with war
dependency's. Then I want the install/package goal to do the following.

    - unpack war dependency's (not required but...)
    - compile the current project with a classpath containing
WEB-INF/classes and WEB-INF/lib from all specified war dependency's.
    - assemble a new war containing files from current project and war
dependency's. Possibly merging web.xml or simply failing if more then
one web.xml, or any other file, is found.

I also want to be able to do "maven run-my-init-db-java-class" but this
could be done in a separate maven project depending on the resulting war.

This use case can also be applyed if I want to be able to install my war
into a remote repo without including properties with config data such as
passwords.

/ Mikael


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to