try replacing:
<j:expr value="${dep.setProperty('war.bundle','false')}" />
with:
<j:set var="dummy">${dep.setProperty('war.bundle','false')}</j:set>
The j:set bit just swallows the output, you could leave it off.
You can also do a postGoal on war:webapp and delete it :)
I'm interested in your use case for this. I'm a strong proponent of
having a WAR work everywhere from dev to production without
modification (except perhaps to change the compiler flags to remove
debug, etc).
- Brett
On Wed, 29 Dec 2004 15:36:31 -0700, Travis Stevens
<[EMAIL PROTECTED]> wrote:
>
> > Wouldn't it be easier to remove the war.bundle property during
> > development and putting it back later if you need it? Worst case,
> > adding a copy to put it in your WEB-INF/lib before building a WAR also
> > seems more straight-forward...
>
> This is what I will probably end up doing, but Maven is more about
> automation. There are currently three things that must take place
> during development that would not take place in the production
> environment. I think the more straight forward approach is to specify a
> development flag which then copies resources and such into the
> appropriate place instead of supplying a readme file with manual steps
> to take.
>
> -Trav
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
