You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2008/06/03 23:20:45 UTC
[jira] Resolved: (WICKET-1683) wicket-contrib-datepicker
compatibility
[ https://issues.apache.org/jira/browse/WICKET-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-1683.
-----------------------------------
Resolution: Won't Fix
this issue should be reported in the wicket-stuff jira
> wicket-contrib-datepicker compatibility
> ---------------------------------------
>
> Key: WICKET-1683
> URL: https://issues.apache.org/jira/browse/WICKET-1683
> Project: Wicket
> Issue Type: Test
> Components: wicket-extensions
> Affects Versions: 1.3.3
> Environment: Windows XP Professional SP3, Apache Tomcat 6.0, Apache Wicket 1.3.3
> Reporter: fallout
> Fix For: 1.3.3
>
>
> Hi.
> It is written here http://wicketstuff.org/confluence/display/STUFFWIKI/wicket-contrib-datepicker that 'Package names have been kept the same, so this is a 100% backwards-compatible direct drop-in replacement for the old component.'.
> But really the package names are different. Wicket 1.3.3 version has packages started from org.apache.wicket... but the wicket-contrib-datepicker-1.2.zip has packages started from wicket....
> So it means that it is not drop-in replacement.
> Are you going to support old wicket calendar component for new versions of wicket?
> Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.