In the serialization exception message, include the class whose type signature was not found.

Change-Id: I45f1a195b0c5fc567af4bce13c2489baf8b2b18d
Review-Link: https://gwt-review.googlesource.com/#/c/4960/
Fixes ResourceOracleImplTest by restoring class path entry get/set for all AbstractResources.

Also added a non-classpath constructor for ZipFileResource to work with zip libraries.

Change-Id: I8d9fa84f48e4c84503aad38d61832b2623cb5464
Implements UrlResource to adapt URL instances to the Resource interface

This is useful when copying data that was not loaded via the normal
resource system (for example .gwt.xml files) into systems that expect a
resource object (for example a library builder).

Change-Id: Ife9907407399d728ce29bf9a40a24d1b421cb1eb
Adds a visitor capable of collecting reboundTypes even in an AST
that has not yet been unified.

In monolithic compilation the act of AST unification and GWT.create()
rebinding were combined in UnifyAst. But with separate compilation
these steps need to be separate and thus the need for a rebound type
collection process that can function even prior to unification.

Change-Id: Iaeb55573c9942cc864639ed7c6d91f736d15cfdb
Revert "Implements UrlResource to adapt URL instances to the Resource interface"

This reverts commit 88c5fc49eb4526f1780f183e3ce9826fd378aa02.

Change-Id: I7b6004c7c1812da74e22e4d871cc1d12415825a2
Adds a "combined" resource oracle view of multiple other oracles.

Useful when the resource oracles being combined are very different
in nature. For example one that surfaces resources on disk for a
module and one that surfaces resources in a set of precompiled
libraries.

Change-Id: Ic7da3168c40bb6a24da1b4fa47787e032f97fff2
Review-Link: https://gwt-review.googlesource.com/#/c/4983/
Implements UrlResource to adapt URL instances to the Resource interface

This is useful when copying data that was not loaded via the normal
resource system (for example .gwt.xml files) into systems that expect a
resource object (for example a library builder).

Change-Id: Ida7a44e59519d11e10453bd0e3c1c9901f2bed0b
Add Map support to RequestFactory

Properties of the key and value types can be loaded using with()
and a special map properties syntax. The syntax simply requires
adding "keys" and/or "values" after the map property name e.g.
.with("someMap.keys.propertyInKeyType") or
.with("someMap.values.propertyInValueType")

Note that null keys are not supported.

Bug: issue 5524
Change-Id: I6dd3c8a9862473954a72ccee96212c20d9198b22
fix compile error in mailbox sample

Change-Id: I7751396bdd2a26caf42c0686be68708b8e681d93
Give developers control on fragment merge via the Class literal parameter in GWT.runAsync().

The code splitter will put the code for all runAsyncs that specify the same class literal
as the first parameter in the two parameter GWT.runAsync call in the same code fragment.

Fixes issue 8130.

Change-Id: Icc445f880dbefca8fc5d3738f93f3e7de8ef05e6
Adds a unit cache that finds compilation unit instances in a library group.

ContentId based lookups are not supported since having multiple versions
of the same compilation unit in a set of libraries would be an error.

Removals are not supported since libraries are immutable and the
removals would only be needed if library contents were invalid.

This class is an integral part of reusing previous work (previously
compiled compilation units) from library files created in previous
compiles of dependency library modules.

Change-Id: I9b67f8fecbcad56a0b1197532fccc811ff3030c1
Review-Link: https://gwt-review.googlesource.com/#/c/4990/
Fixes comment about requiring class literals in GWT.runAsync calls to be unique.

Using the same class literal in different GWT.runAsync calls makes the code
splitter place the corresponding code in the same fragment.

Also fixed the ordering of members in CodeSplitter.java.

Change-Id: I2e4bc379f669791390edbd02daf20f2e33200934
Revert "Add Map support to RequestFactory"

This reverts commit 1a8c2ccf9b601fd383fd1cb9c8f8db9048434842.

Change-Id: I8de39b5831caea046730cd85893953307ef7c886
Rescue Arraytype from ArrayPrototypePatcher

Change-Id: I7c36c7a9729db02b22fc5c078cd1e8a68880a567
Add Map support to RequestFactory

Properties of the key and value types can be loaded using with()
and a special map properties syntax. The syntax simply requires
adding "keys" and/or "values" after the map property name e.g.
.with("someMap.keys.propertyInKeyType") or
.with("someMap.values.propertyInValueType")
Note that null keys are not supported.

Bug: issue 5524
Change-Id: I6baf78610f841a250f8771c13a97d396a94b01ba
Adds several generators and classes as well as a couple of Condition
changes related to runtime rebinding.

Runtime rebinding is needed for separate compilation since static
compile time rebinding is only possible when in possession of complete
global knowledge.

Change-Id: I47846755d0fda7068676bb106b84834d584f20fe
Review-Link: https://gwt-review.googlesource.com/#/c/4991/
Ensure int values for pixels.

Browsers started to send sub pixel values for things like
element.getBoundingBox().top.

Added methods that return double to DOMImpl and Element
and modified existing ones to use it with a fast round (e.g. width | 0)

This patch does not touch IE6 and IE8 DOM impl since this is not an issue
with those two.

Change-Id: I32f1eb1d9b8591d71d3662455c57bfd4ad696661
Adds a "dynamic property oracle" that when passed to a generator,
helps discover all possible generator output (given the limited
scope of currently known legal property values) and the combination
of property values associated with each output.

The collected information makes it possible to synthesize runtime
rebind rule class implementations and ensures the creation of all
generator output without depending on the existing permutation
system.

Change-Id: I67118b0f28e9a93479b54679c5bbf120de20cdf3
Replace gwt.svnrev with gwt.gitrev.

Change-Id: I3f28322bd6c127b5cfff968c178fa27d001679b8
Fix for error caused when two variables at different scopes had the same name.

The GWT compiler does not represent explicitly block scopes but allows
two different local variables at different block scopes have the same name.

It is assumed that variables with the same name are guaranteed to have non
intersecting lifetimes and can be coalesced when lowering to the JavaScript
AST representation.

The Java AST produced initially by GwtAstBuilder upholds the above mentioned
assumption but the copy propagation optimization in the DataflowOptimizer does
not. It is not clear whether another optimization pass violates this assumption;
hence the fixup is done prior to JavaScript AST generation.

Fixes issue 7045, and issue 8304.

Change-Id: I1d6faae19dc228a3e8ef4c59bebf4297f04b5413