tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <...@tapestry.apache.org>
Subject [jira] Closed: (TAPESTRY-1843) Tapestry should have a "production mode" (vs. development mode)
Date Thu, 24 Jan 2008 19:58:35 GMT

     [ https://issues.apache.org/jira/browse/TAPESTRY-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Howard M. Lewis Ship closed TAPESTRY-1843.

       Resolution: Fixed
    Fix Version/s: 5.0.10

> Tapestry should have a "production mode" (vs. development mode)
> ---------------------------------------------------------------
>                 Key: TAPESTRY-1843
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1843
>             Project: Tapestry
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.0.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.0.10
> It's very common for people to deactivate certain features in production, such as the
verbose exception report.  Further, certain safe things (such as using automagically stripped/compressed
JavaScript) are desirable only in production, but not in development.  Tapestry should define
a symbol, tapestry.production-mode, that defaults to "true".  Developers can override this
by adding -Dtapestry.production-mode=false to the launch command line.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message