Tapestry
  1. Tapestry
  2. TAPESTRY-1843

Tapestry should have a "production mode" (vs. development mode)

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.5
    • Fix Version/s: 5.0.10
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      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.

        Activity

        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12569313 ] jira [ 12592149 ]
        Mark Thomas made changes -
        Workflow jira [ 12415471 ] Default workflow, editable Closed status [ 12569313 ]
        Howard M. Lewis Ship made changes -
        Resolution Fixed [ 1 ]
        Fix Version/s 5.0.10 [ 12312936 ]
        Status In Progress [ 3 ] Closed [ 6 ]
        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Assignee Howard M. Lewis Ship [ hlship ]
        Howard M. Lewis Ship created issue -

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development