I posted something a while ago about the wicket-contrib-dojo-0.3.1
incompatability with wicket-1.2.x. I'd like to use some Dojo features
with the latest wicket release, so Matt Carlson and I will be working
on some code fixes for the Wicket-Dojo source code. If we get it
working in the
Hi,
Unfortunately they are bussy with other projects (though doing those
with Wicket I think). Would you two be interested in taking over that
project?
Cheers,
Eelco
On 4/26/06, Jeff Lin [EMAIL PROTECTED] wrote:
I posted something a while ago about the wicket-contrib-dojo-0.3.1
Well we tried maven clean dist and maven clean jar:install. Even
manually deleting the jar from the repository first, and just linking to
an external jar instead of the reposistory We even tried building on
another machine to prevent obscure caching errors. We tried running
the
Compare what's in the jar with what's in your actual class path in
Eclipse. The maven project files look ok to me though. I'll give it a
look later today.
Eelco
On 12/1/05, Marco van de Haar [EMAIL PROTECTED] wrote:
Well we tried maven clean dist and maven clean jar:install. Even
manually
We've released a SNAPSHOT release of wicket-contrib-dojo, which is not
much more then our 0.3 release with a few fixes:
-maven building should work now for both contrib-dojo and
contrib-dojo-examples
-the examples WAR file should be deployable in a Jetty instance now
-FXValidationAjaxHandler
Maybe it's in a cache somewhere locally, or you build it without
issues maven clean first (which you should always do in order to have
a clean build).
To fix it: test with a SNAPSHOT first. If that works and you don't
want to make a new release (/and/ you didn't upload the version
anywhere yet,
