[jira] [Updated] (TAP5-890) Provide constants for ids of most important contributions to OrderedConfiguration and MappedConfiguration

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade updated TAP5-890:
--------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> Provide constants for ids of most important contributions to OrderedConfiguration and MappedConfiguration
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-890
>                 URL: https://issues.apache.org/jira/browse/TAP5-890
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.2
>            Reporter: Igor Drobiazko
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> It is very common use case to contribute to configuration of MasterDispatcher or similar services. In most cases one has to look into the source of TapestryModule. It would be nice to have constants for contributed ids.



--
This message was sent by Atlassian JIRA
(v6.2#6252)