Currently we are at 1.5 RC4. If there are no major problems the next one may be 1.5 Final. Final or RC5 it will be out in ~ 3 weeks from now.
Use https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+1.5when migrating. The problem with Request class can be "solved" with "Optimize imports" feature in the IDE. On Mon, May 16, 2011 at 9:15 PM, Alexandru Artimon < [email protected]> wrote: > I've compiled the latest code from the wicket trunk and when plugging in > the latest jars into our project I've seen that some changes have to be done > in order to use wicket 1.5 (like some package names changed, can't find > org.apache.wicket.Request). > > So I was wandering how far is the 1.5 release ? Because we're usually > including final versions in our project. > > Thanks, > Alex > > > On 05/16/2011 06:28 PM, Martin Grigorov wrote: > >> How to build Wicket is described at >> http://wicket.apache.org/contribute/build.html >> But the patch is only for 1.5. You can't use it in 1.4. >> >> I recommend you to upgrade. >> >> On Mon, May 16, 2011 at 5:16 PM, Alexandru Artimon< >> [email protected]> wrote: >> >> I can try the patch and test, but I only have the wicket 1.4.17 jars. >>> So can I do a code checkout from somewhere? :D >>> Or get a jar that has the patch in it ? >>> >>> >>> >>> On 05/16/2011 05:50 PM, Martin Grigorov wrote: >>> >>> Sounds like https://issues.apache.org/jira/browse/WICKET-3719 >>>> >>>> Can you try the patch there and give feedback ? >>>> If it still fails then a quickstart app or a test case would help us to >>>> improve it. >>>> >>>> On Mon, May 16, 2011 at 4:43 PM, Alexandru Artimon< >>>> [email protected]> wrote: >>>> >>>> Hello, >>>> >>>>> I have a custom wicket html tag that is handled by a component resolver >>>>> to >>>>> automatically generate a component for it. And these components only >>>>> exist >>>>> at the render phase and aren't stored in the page tree. >>>>> >>>>> Now when Ajax is used to update a fragment of the web page, looks like >>>>> the >>>>> components for these wicket html tags were not rendered. So instead of >>>>> getting the desired markup I get only the contents of the original >>>>> markup. >>>>> >>>>> Might this be a bug? It looks like the component resolver doesn't work >>>>> when >>>>> the response is built for the ajax update. >>>>> >>>>> Any ideas/workarounds ? >>>>> >>>>> Thanks again, >>>>> Alex >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com <http://jweekend.com/>
