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 mer
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
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.
- Brett
On 10/21/05, jerome lacoste <[EMAIL PROTECTED]> wrote:
> I need to take a war and add some packages in certain places.
>
> I took the approac
I need to take a war and add some packages in certain places.
I took the approach of using the assembly plugin to repackage the war.
I.e. I have now 2 projects A & B, A packages the war, B takes the war
and a couple of zip files as dependencies, and assemble the whole.
It fails miserably because
