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

Posted to commits@wicket.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/04/07 17:15:12 UTC

[jira] [Commented] (WICKET-5410) Remove setting interfaces

    [ https://issues.apache.org/jira/browse/WICKET-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483337#comment-14483337 ] 

ASF subversion and git services commented on WICKET-5410:
---------------------------------------------------------

Commit bd18b9b11260cc06798b1f9dd72a191ddcc04f41 in wicket's branch refs/heads/grails-maven-integration from [~bitstorm]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=bd18b9b ]

guide changed to comply with WICKET-5410


> Remove setting interfaces
> -------------------------
>
>                 Key: WICKET-5410
>                 URL: https://issues.apache.org/jira/browse/WICKET-5410
>             Project: Wicket
>          Issue Type: Improvement
>            Reporter: Igor Vaynberg
>            Assignee: Martin Grigorov
>             Fix For: 7.0.0-M1
>
>
> We still have separate settings interfaces. mostly this is a legacy design decision when we have a single settings object implement all these interfaces.
> the problem now that we are in semver is that we cannot add new settings in between major releases because doing so requires adding a method to an interface.
> since we do not have a single class implementing multiple interfaces scenario anymore we can get rid of the settings interfaces safely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)