You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Martijn Dashorst <ma...@gmail.com> on 2015/06/18 18:22:43 UTC
Second project migration to wicket 7 status report
My second (big) project migration to Wicket 7 was just started this
afternoon, and consists of roughly 520K lines of Java code, and is
built against our internal wrapper framework, just as the previous
project is, so I can reuse a lot of migration work already done.
This project contained 79 compiler errors caused by Wicket's API
breakage between wicket 6 and 7.
These consisted mostly of custom implementations of IChoiceRenderer. I
was able to go from 79 errors to 9 errors in roughly 1.5 hour.
The remainder errors are 7 caused by the removal of
org.apache.wicket.util.upload.
And 2 caused by ListView's model change from IModel<List<T>> to
IModel<? extends List<T>>, effectively making those lists read only.
Martijn
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Re: Second project migration to wicket 7 status report
Posted by Tobias Soloschenko <to...@googlemail.com>.
Thank you from me, too! Good to get an impression of a migration of a big project.
kind regards
Tobias
> Am 19.06.2015 um 10:44 schrieb andrea del bene <an...@gmail.com>:
>
> Thank you Martijn. Looks quite smooth considering the size of the project :)
>
>> On 18/06/2015 18:22, Martijn Dashorst wrote:
>> My second (big) project migration to Wicket 7 was just started this
>> afternoon, and consists of roughly 520K lines of Java code, and is
>> built against our internal wrapper framework, just as the previous
>> project is, so I can reuse a lot of migration work already done.
>>
>> This project contained 79 compiler errors caused by Wicket's API
>> breakage between wicket 6 and 7.
>>
>> These consisted mostly of custom implementations of IChoiceRenderer. I
>> was able to go from 79 errors to 9 errors in roughly 1.5 hour.
>>
>> The remainder errors are 7 caused by the removal of
>> org.apache.wicket.util.upload.
>>
>> And 2 caused by ListView's model change from IModel<List<T>> to
>> IModel<? extends List<T>>, effectively making those lists read only.
>>
>> Martijn
>
Re: Second project migration to wicket 7 status report
Posted by andrea del bene <an...@gmail.com>.
Thank you Martijn. Looks quite smooth considering the size of the project :)
On 18/06/2015 18:22, Martijn Dashorst wrote:
> My second (big) project migration to Wicket 7 was just started this
> afternoon, and consists of roughly 520K lines of Java code, and is
> built against our internal wrapper framework, just as the previous
> project is, so I can reuse a lot of migration work already done.
>
> This project contained 79 compiler errors caused by Wicket's API
> breakage between wicket 6 and 7.
>
> These consisted mostly of custom implementations of IChoiceRenderer. I
> was able to go from 79 errors to 9 errors in roughly 1.5 hour.
>
> The remainder errors are 7 caused by the removal of
> org.apache.wicket.util.upload.
>
> And 2 caused by ListView's model change from IModel<List<T>> to
> IModel<? extends List<T>>, effectively making those lists read only.
>
> Martijn
>