You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Wayne W <wa...@gmail.com> on 2013/12/30 17:45:20 UTC

Migrating from 1.4.21 to 6

Hi All,

I'm wanting to upgrade to the latest version of wicket but am worried about
the possible impact. Also I'm wanting to know the best migration plan. Do
you think it would be best to jump straight to 6 or first upgrade to 5?

Any tips or ideas would be much appreciated.

thanks

Re: Migrating from 1.4.21 to 6

Posted by sujitkirve <su...@gmail.com>.
The best thing is to jump to version 6, there are lot difference  between
version 1.5 & 6.0 ...




On Mon, Dec 30, 2013 at 10:17 PM, Wayne W [via Apache Wicket] <
ml-node+s1842946n4663324h20@n4.nabble.com> wrote:

> Hi All,
>
> I'm wanting to upgrade to the latest version of wicket but am worried
> about
> the possible impact. Also I'm wanting to know the best migration plan. Do
> you think it would be best to jump straight to 6 or first upgrade to 5?
>
> Any tips or ideas would be much appreciated.
>
> thanks
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-wicket.1842946.n4.nabble.com/Migrating-from-1-4-21-to-6-tp4663324.html
>  To start a new topic under Users forum, email
> ml-node+s1842946n1842947h33@n4.nabble.com
> To unsubscribe from Apache Wicket, click here<http://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1842946&code=c3VqaXRraXJ2ZUBnbWFpbC5jb218MTg0Mjk0NnwyMDcxMzU2OTIz>
> .
> NAML<http://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>



-- 
Thanks & Regards

Sujit Kirve




--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Migrating-from-1-4-21-to-6-tp4663324p4663344.html
Sent from the Users forum mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Migrating from 1.4.21 to 6

Posted by Martijn Dashorst <ma...@gmail.com>.
Typically I upgrade our applications one version at a time... Fix all
warnings related to wicket (or I rather have all warnings == 0) and
then test the application and fix any mishaps resulting from this
upgrade. Then you can commit the (working) upgrade and move to the
next version.

But you can also do it in one go, depends on the size of the
application, complexity and what you feel comfortable with...

Martijn


On Mon, Dec 30, 2013 at 5:45 PM, Wayne W <wa...@gmail.com> wrote:
> Hi All,
>
> I'm wanting to upgrade to the latest version of wicket but am worried about
> the possible impact. Also I'm wanting to know the best migration plan. Do
> you think it would be best to jump straight to 6 or first upgrade to 5?
>
> Any tips or ideas would be much appreciated.
>
> thanks



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Migrating from 1.4.21 to 6

Posted by Francois Meillet <fr...@gmail.com>.
You should migrate directly to verion 6.
If you have 200 K LoC on the web tier, you should budget between one to three months, depending the amount of specific code that has been written to improve the 1.4 api.

François Meillet
Formation Wicket - Développement Wicket





Le 2 janv. 2014 à 10:48, Wayne W <wa...@gmail.com> a écrit :

> I have about 200,000 lines of code. I don't have time to rewrite the app.
> Is there a fundamental difference the requires a rewrite?
> 
> 
> On Tue, Dec 31, 2013 at 4:34 PM, Martin Sachs <sa...@gmail.com>wrote:
> 
>> Hi,
>> 
>> i would mirgate to 6 directly, if your application is relativ small and
>> without special requesthandlings, webtrackings and last but not least
>> javascript dependencies to other framework than wicket.
>> 
>> e.g. for an application with round about 5.000 lines of code its easier
>> to update. For big applications (>20.000 LoC) an rewrite with wicket-6
>> could be better and cleaner with the same effort as updating.
>> 
>> cheers and good luck ;)
>> 
>> Am 30.12.2013 17:45, schrieb Wayne W:
>>> Hi All,
>>> 
>>> I'm wanting to upgrade to the latest version of wicket but am worried
>> about
>>> the possible impact. Also I'm wanting to know the best migration plan. Do
>>> you think it would be best to jump straight to 6 or first upgrade to 5?
>>> 
>>> Any tips or ideas would be much appreciated.
>>> 
>>> thanks
>>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>> 
>> 


Re: Migrating from 1.4.21 to 6

Posted by Wayne W <wa...@gmail.com>.
I have about 200,000 lines of code. I don't have time to rewrite the app.
Is there a fundamental difference the requires a rewrite?


On Tue, Dec 31, 2013 at 4:34 PM, Martin Sachs <sa...@gmail.com>wrote:

> Hi,
>
> i would mirgate to 6 directly, if your application is relativ small and
> without special requesthandlings, webtrackings and last but not least
> javascript dependencies to other framework than wicket.
>
> e.g. for an application with round about 5.000 lines of code its easier
> to update. For big applications (>20.000 LoC) an rewrite with wicket-6
> could be better and cleaner with the same effort as updating.
>
> cheers and good luck ;)
>
> Am 30.12.2013 17:45, schrieb Wayne W:
> > Hi All,
> >
> > I'm wanting to upgrade to the latest version of wicket but am worried
> about
> > the possible impact. Also I'm wanting to know the best migration plan. Do
> > you think it would be best to jump straight to 6 or first upgrade to 5?
> >
> > Any tips or ideas would be much appreciated.
> >
> > thanks
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

Re: Migrating from 1.4.21 to 6

Posted by Martin Sachs <sa...@gmail.com>.
Hi,

i would mirgate to 6 directly, if your application is relativ small and
without special requesthandlings, webtrackings and last but not least
javascript dependencies to other framework than wicket.

e.g. for an application with round about 5.000 lines of code its easier
to update. For big applications (>20.000 LoC) an rewrite with wicket-6
could be better and cleaner with the same effort as updating.

cheers and good luck ;)

Am 30.12.2013 17:45, schrieb Wayne W:
> Hi All,
>
> I'm wanting to upgrade to the latest version of wicket but am worried about
> the possible impact. Also I'm wanting to know the best migration plan. Do
> you think it would be best to jump straight to 6 or first upgrade to 5?
>
> Any tips or ideas would be much appreciated.
>
> thanks
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Migrating from 1.4.21 to 6

Posted by Martin Grigorov <mg...@apache.org>.
Hi,

I would migrate first to 1.5.10 and then to 6.12.
In case of issues I'd check the migration guides, then the mailing list
archives and finally ask a new question here.

Good luck!
On Dec 30, 2013 6:46 PM, "Wayne W" <wa...@gmail.com> wrote:

> Hi All,
>
> I'm wanting to upgrade to the latest version of wicket but am worried about
> the possible impact. Also I'm wanting to know the best migration plan. Do
> you think it would be best to jump straight to 6 or first upgrade to 5?
>
> Any tips or ideas would be much appreciated.
>
> thanks
>