Have there been that many changes since 1.4-rc4? I just released rc4 like three weeks ago. Are we talking about the same rc4?
-- Jeremy Thomerson http://www.wickettraining.com On Sat, May 23, 2009 at 9:41 PM, Brill Pappin <[email protected]> wrote: > I don't actually have commit to wicketstuff, but cudos for having all > modules build and all tests passing, I'm able to build without any trouble > and deploy into our local repo on the first try. > I don't mind help get it up though, particularly if it gets things working > again. > > As of last night, all modules in wicketstuff-core are building and all tests > passing, but thats against the current wicket-1.4-SNAPSHOT so I'm not sure > about rc4 (I think it might not build against rc4 because of the mentioned > issues). > > I think you might have to wait until they do a new release, then tag your > repo immediately and release from there, there have been a lot of changes in > wicketstuff-core since wicket-rc4. > You might also be able to check the date of rc4 in the wicket svn and tag a > revision of wicketstuff-core for that date (risky, but might just work). > > - Brill > > > > On 23-May-09, at 10:03 PM, Jeremy Thomerson wrote: > >> What we really need to do (and I haven't had time to do) is cut a >> release of wicketstuff 1.4-rc4 to match wicket's recent release. That >> was the reason I went through all the effort of getting all of the WS >> core projects together - so that they could be numbered with releases >> that matched Wicket's. >> >> So, if you have time and are willing to work on something, please make >> sure all of the projects work and build against Wicket 1.4-rc4 and >> then make a tag of that moment in the repo. I can do the release from >> there if you send me a link. I started to do a release a couple weeks >> ago right after I built the core release, but some things weren't >> compiling / working and I didn't have the time to fix all of those >> projects. >> >> -- >> Jeremy Thomerson >> http://www.wickettraining.com >> >> >> >> >> On Fri, May 22, 2009 at 8:26 PM, Brill Pappin <[email protected]> wrote: >>> >>> Over the last week I've been running into no end of NoSuchMethod >>> errors, particularly between the wicket 1.4-SNAPSHOT and the wicketstuff >>> 1.4-SNAPSHOT. >>> They both are snapshots, so this is expected now and then, however they >>> don't seem to be being fixed. >>> In all cases so far, the exceptions that popup during runtime reflection >>> and >>> a common theme is the ModalWindow classes. >>> For instance: >>> Caused by: java.lang.NoSuchMethodError: >>> >>> org.apache.wicket.extensions.ajax.markup.html.modal.ModalWindow.setPageMapName(Ljava/lang/String;)V >>> at >>> >>> org.wicketstuff.calendarviews.LargeView.initializeDetailModalWindow(LargeView.java:103) >>> There is another that I don't have off the top right now, but it's >>> similar >>> (also in ModalWindow, although not the same error). >>> In general one of the reasons I chose to work with Wicket is the easy way >>> it >>> can be tested. >>> So, to that end I would like to recommend to the WIcket Stuff developers >>> that *aLl example apps* have unit tests. Unit testing the examples would >>> more than likely expose these problems early. To begin with, any library >>> that uses ModalWindow should have unit tests added. >>> I'm in the process now of checking out the wicketstuff source so I can >>> start >>> trying to fix some of this stuff, time permitting myself. >>> - Brill >>> >>> >> >> --------------------------------------------------------------------- >> 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]
