Running a script on config files is not a big deal for an upgrade. Most commercial software probably does that with (or without) our acknowledgement. If the script were consistent it could always be packaged with tomcat to aid in upgrades.
The way apps are deployed (configured) is new and will have gotchas like this. But the code is open for anyone to say "I don't like that" and propose their change. (Or fork if you change isn't made)
-Tim
Gerry Reno wrote:
Tim, Is this definitive? I was hoping this would not be the case. I think that requiring users to run content replacement scripts against their config files to accomplish an upgrade will definitely end up being problematic.
Gerry
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
