Hi guys,
I have just upgraded a large project from wicket 1.3 to 1.4(.18) and needed to
update wicketstuff-animator.
I now have a patch against the import-backup on github but have no idea how /
where to contribute this.
Should I fork the backup (weird) or can I start a new repo from the code
t; I have just upgraded a large project from wicket 1.3 to 1.4(.18) and
>> needed to update wicketstuff-animator.
>> I now have a patch against the import-backup on github but have no idea
>> how / where to contribute this.
>>
>> Should I fork the backup (weird) or ca
fork the project into your github account, commit the patch, and
create a pull request.
-igor
On Tue, Apr 17, 2012 at 2:52 PM, andy wrote:
> Hi guys,
>
> I have just upgraded a large project from wicket 1.3 to 1.4(.18) and
> needed to update wicketstuff-animator.
> I now have
Hi guys,
I have just upgraded a large project from wicket 1.3 to 1.4(.18) and
needed to update wicketstuff-animator.
I now have a patch against the import-backup on github but have no idea
how / where to contribute this.
Should I fork the backup (weird) or can I start a new repo from the code
in
Hello,
I would like to try out wicketstuff-animator but when trying out the
basic example on the official page
(http://wicketstuff.org/confluence/display/STUFFWIKI/wicketstuff-animator)
with wicket 1.4.4 I get an exception. I guess it's because
wicketstuff-animator depends on wicket 1.3.3
