Re: altering war.bundle property at maven runtime

[Travis Stevens]

Brett Porter wrote:
try replacing:
<j:expr value="${dep.setProperty('war.bundle','false')}" />
with:
<j:set var="dummy">${dep.setProperty('war.bundle','false')}</j:set>
I still couldn't get this to work.  Is this the correct syntax to set a 
property?  I was guessing the first time.  This is confusing to be 
because the Dependency class does not have a setProperty method, so I'm 
not sure how these properties are even being handled by maven (or jelly).

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).
Well, if you must know ;).  We use a proprietary set of java class 
libraries.  There is a class that needs to be initialized before 
anything can be done with the webapp.  This initialization longer than a 
minute.  Can you image waiting a minute when you reloaded the context 
just to check out a minor change?  So I found that a little tomcat hack 
which can get around this by keeping that long loading class in a 
separate context which does not get reloaded and the main context can 
just grab that instance from the other context.  Context reload times 
are then normal.

This is a hack and tomcat even notes that the cross context loading 
should not be done in a production environment, so we only do this for 
development.

It's not very interesting and eventually this needs to be refactored, 
but we are stuck with it right now.

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