GWT Support against Google Collections Source / Single jar

[GoogleCodeExporter]

Hey,

First of all your great work is much appreciated.

After struggling a bit to get another library to integrate with GWT (in that 
case AntLR 
3), I thought I would take what I had learnt and hopefully add something back 
to you 
guys.

As I'm sure your aware a GWT client project can't refer directly the 
GoogleCollection 
source. The collection's ant needs to be run and the GWT client needs to point 
to the 
generated jar (actually both jar need to be referenced if collections as the 
IDE needed 
the generated class files).

A solution to this is to put includes and or excludes in the source elements of 
the 
module. This negates the need for the @GwtCompatible annotations.

Attached is the augmented Collect.gwt.xml file that I am using.

For more details on the restrictions of the include/exclude elements (or 
attributes) 
please see
http://code.google.com/p/google-web-toolkit/issues/detail?id=4559

Regards
Gary

Original issue reported on code.google.com by miller.garym on 8 Feb 2010 at 12:03

Attachments:

• Collect.gwt.xml

[GoogleCodeExporter]

Sadly, the fact that you can't trivially use the library in GWT in the way you 
expect 
is intentional:

http://groups.google.com/group/google-collections-
users/browse_thread/thread/af864f4d45f0012f

It is a priority for us in the coming months, but for most features in the 
library it 
takes considerably more effort to make it work in GWT than it takes to create 
the 
feature in the first place.

Original comment by kevinb@google.com on 8 Feb 2010 at 4:38

• Changed state: Invalid

[GoogleCodeExporter]

This issue has been migrated to GitHub.

It can be found at https://github.com/google/guava/issues/<id>

Original comment by cgdecker@google.com on 1 Nov 2014 at 4:16

• Added labels: MigratedToGitHub

[GoogleCodeExporter]

Original comment by cgdecker@google.com on 3 Nov 2014 at 9:10

• Added labels: Restrict-AddIssueComment-Commit