if local builds are being run using jetty:run there are some tricks to allow
jetty to add the file to the effective webapp so that the war never needs
context.xml and there is just one and only one war built (thus avoiding the
nasty profile produces different artifact complaint that people make after a
while with profiles)

- Stephen

---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 28 Sep 2011 19:51, "Wayne Fay" <[email protected]> wrote:
>> We use context.xml in our local builds, but when building a war for
>> other environments, we would like to not include the context.xml file.
>>
>> Any ideas on how to exclude context.xml for non-local builds?
>
> Any time you have a question like this, the answer is almost always
> "use a profile."
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

Reply via email to