You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Jeremy Thomerson (JIRA)" <ji...@apache.org> on 2010/10/17 01:46:25 UTC

[jira] Resolved: (WICKET-2729) Proposal to reopen WICKET-2696 to include the patch + unit test into next wicket release

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

Jeremy Thomerson resolved WICKET-2729.
--------------------------------------

    Resolution: Won't Fix
      Assignee: Jeremy Thomerson

I won't agree to reopen this issue.  Like Igor said on the original issue, it's super simple for you to roll your own.  Wicket isn't a collection of components for every hedge case.  It's a framework that makes it extremely easy for you to roll your own with some very useful components that fit the 95% case.  Unfortunately, I also disagree with the argument "the problem is maintaining it" because what it really means is that it would be better if someone else maintained it.  Volunteers who aren't getting paid for maintaining it :)

> Proposal to reopen WICKET-2696 to include the patch + unit test into next wicket release
> ----------------------------------------------------------------------------------------
>
>                 Key: WICKET-2729
>                 URL: https://issues.apache.org/jira/browse/WICKET-2729
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.4.6
>            Reporter: Martin Makundi
>            Assignee: Jeremy Thomerson
>            Priority: Minor
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Hi!
> This is a proposal to reopen WICKET-2696 to include the patch + unit test into next wicket release. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.