On Mon, Nov 25, 2013 at 7:01 PM, Jörg Hohwiller <
[email protected]> wrote:

> Hi there,
> I posted in GWT community on g+ about my *JSR 310* backport I created and
> my super-sourced GWT code.
> Stephen Habermann posted:
>   Wow, 13000 passing tests is amazing. Great work!  You should post about
> your progress on the gwt-contrib list
>
> (I am still unsure about when to post to groups and when g+)
>
> So here I am. You can find all my work and changes from here:
> https://github.com/m-m-m/mmm/issues/83
>
> I am looking forward for your feedback and discussion. It will be my
> pleasure to contribute my work to the GWT project.
> However, I am not clear about the permissions required from the original
> authors of threeten since I simply forked their codebase and keept their
> headers and copyrights in my project.
> For GWT this has to be transferred and I assume we would need permissions
> from Stephen Colebourne, Michael Santos and all the others.
>

The BSD-licensed parts shouldn't be any problem to import, but you have a
few files with Oracle licenses which aren't going to work.

Also, the GWT i18n code will need to be updated to support this as well.

There are a few things which are going to be very hard to support   As Jens
mentioned, ZoneRulesProvider needs an async API so it can fetch the
necessary data from a server, so we can't provide a compatible API.  We can
provide a GWT-specific version (under a different package), so shared code
can deal with ZoneRules/etc but getting them will be different in client vs
server code.

Have you looked at generated code size?  There are also a few places where
it appears to rely on overflow behavior, which isn't guaranteed in GWT as
an int is actually represented by a JS Number under the hood.

-- 
John A. Tamplin

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to