[
https://issues.apache.org/jira/browse/WICKET-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934173#action_12934173
]
Hudson commented on WICKET-1945:
--------------------------------
Integrated in Apache Wicket 1.5.x #536 (See
[https://hudson.apache.org/hudson/job/Apache%20Wicket%201.5.x/536/])
fixed WICKET-1945 make wicket's configuration type an enum
Issue: WICKET-1945
> make wicket's configuration type an enum
> ----------------------------------------
>
> Key: WICKET-1945
> URL: https://issues.apache.org/jira/browse/WICKET-1945
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Reporter: Peter Ertl
> Assignee: Juergen Donnerstag
> Fix For: 1.5-M4
>
> Attachments: RuntimeConfigurationTypesEnum.patch
>
>
> I would suggest that (starting with wicket 1.5.x) the wicket configuration
> type should be converted to an enum.
> current:
> String org.apache.wicket.Application.getConfigurationType()
> future:
> ConfigurationType org.apache.wicket.Application.getConfigurationType()
> ------------
> package org.apache.wicket;
> public enum ConfigurationType
> {
> DEVELOPMENT, DEPLOYMENT
> }
> enum have a lot of benefits, e.g. cover all cases in a case block or having
> no upper- or lower-case inconsistencies.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
