Currently a Tapestry app can run either in production mode or not production
mode (let's say test mode). Frequently this true/false decision is not
sufficient. For example, we have three different environments the
application is deployed to: test, integration and production. So a
three-value decision is needed.

I would like to deprecate the tapestry.production-mode symbol in favour of
tapestry.app-mode. The new symbol would take one of the values "test",
"integration", "production" (let's say a enum Mode). Any objections?

-- 
Best regards,

Igor Drobiazko
http://tapestry5.de

Reply via email to