You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2013/05/17 00:59:16 UTC

[jira] [Updated] (TAP5-2040) TapestryAppInitializer should have access to system properties; this is a reversion in 5.4

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

Howard M. Lewis Ship updated TAP5-2040:
---------------------------------------

    Summary: TapestryAppInitializer should have access to system properties; this is a reversion in 5.4  (was: TapestryAppInitializer of T5.4-alpha-1 cannot access system properties)
    
> TapestryAppInitializer should have access to system properties; this is a reversion in 5.4
> ------------------------------------------------------------------------------------------
>
>                 Key: TAP5-2040
>                 URL: https://issues.apache.org/jira/browse/TAP5-2040
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Kristian Marinkovic
>            Assignee: Howard M. Lewis Ship
>
> The TapestryFilter class in T5.4-alpha-1 does not use the SystemPropertiesSymbolProvider as it did in T5.3.6. As a consequence the TapestryAppInitializer cannot access system properties such as tapestry.disable-default-modules to control whether default modules are loaded or not. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira