Fixed name clash in uibinder when a field is named "owner"

bug: issue 7327
Change-Id: Id9e1a77433a09e913e8ef045c63b3f5bff4bbf17
Added @charset rule skipping

bug: issue 6736
Change-Id: I28e867b39cb1755e9bd132f2d4ddd960c21ee076
Makes LibraryBuilder path string encoding more forgiving.

When compiling actual applications Generator execution creates some
synthetic resources with an unusual path character (":"). Library
serialization was guarding against usage of this character, but it
has been changed to allow it. (This was originally correct but was
broken during out-of-context cleanup/review of the builder code).

Added a TODO to unify the Compiler on some fast and consistent
serialization library (probably protobuf) rather than the current
mixture of slow Java serialization, some protobuf, and custom
serialization.

Change-Id: Id4ef7477f3b81cf6a8b7c5eea6914a150d396fcf
Review-Link: https://gwt-review.googlesource.com/#/c/5246/
Fixes namer output for package-info classes.

JDT compilation of package-info.java classes results in the
creation of AST name nodes containing "package-info".
"-" is an illegal character in function names in output
javascript. So the javascript namers have been updated to
fix it.

Previously this was not a problem because this "-" character
was only in package-info classes and the Pruner was
removing those classes. But separate compilation does not
run the pruner, thus revealing this issue.

Change-Id: Ia322dadd36f2e117a3024cf3ed0f2cee8bfcb873
Adds a StatementRanges combining utility.

The Link system uses a StatementRanges object to know
how to and how much Javascript to write to disk. When writing
the combined Javascript from previously compiled libraries (as
part of separate compilation) it becomes necessary to combine
the StatementRanges for those libraries. Thus this change.

We want to enable separate compilation because it will be
faster than monolithic compilation.

Change-Id: I33879e213097c6335ea6c2369ad73dc274c6c8ea
Adds separate compilation flags and options.

Unlike the normal compiler entry point the separate compiler
entry point needs to be informed of precompiled input
libraries, the destination of its output library and whether
to perform linking (as linking is only performed in the last
separate compilation at the top of a compile tree).

So these options and args make it possible to drive the
separate compiler, which is deseriable since separate
compilation is faster.

Change-Id: I645f37d42b14cdecb3fd62e56cc395639a4e36bf
Review-Link: https://gwt-review.googlesource.com/#/c/5247/
Changes to make subclassing easy.

Change-Id: I0c0604b70f72403f758a482b470c6b09307285c0
Review-Link: https://gwt-review.googlesource.com/#/c/5171/
Fixes an Oracle config property lookup bug.

Out of context cleanup/review of DynamicPropertyOracle introduced a
bug by confusing com.google.gwt.dev.cfg.ConfigurationProperty and
com.google.gwt.core.ext.ConfigurationProperty.

Fixed the bug, added a regression test and added a TODO to get rid
of this duplicate class name confusion.

Change-Id: I0f7f4770ee7103a8358163e6cd986be6a04bd679
Adds RuntimePropertyRegistry for runtime rebinding.

The RuntimePropertyRegistry is necessary because runtime rebinding
depends on the execution of condition checks embedded in rebind rules,
and these condition checks depend on property value lookups which it
provides.

Runtime rebinding is needed for separate compilation since static
compile time rebinding is only possible when in possession of complete
global knowledge and thus can only be done in monolithic compiles.

Separate compilation is wanted because it makes things faster by
reducing the amount of work necessary when only a couple of files
have changed and also by making it possible to run some work in
parallel.

Change-Id: I5f688e679a1dab2fa95f6a451a779b7201aee93d
Deprecates AsyncProxy

Deprecated AsyncProxy due to lack of usage and very limited use cases.
Will be made available as third-party library.

Change-Id: I8295f44e00cf9c26b0fef024dbae93f7e1c9d83a
Adds intelligent rerun metadata to generators.

This is metadata (related property names and property/type output
instability) that can be used to determine when and on what scope
of input to run a particular generator during separate compilation.

Without this metadata the only safe way to run generators would
be to defer all of them to a global pass at the end of separate
compilation, which would eliminate any generator result caching and
generator execution parallelism.

As a result, having and using this generator metadata is an
important part of making separate compilation fast.

Change-Id: I763a02a41a5abfd522852b0ad29e200548316c6f
Review-Link: https://gwt-review.googlesource.com/#/c/5243/
Upgrades HtmlUnit and it dependencies

Some major upgrades:
  /htmlunit
  /jetty
  /apache/commons
  /apache/http
  /xerces
  /tomcat/servlet-api

Fixes issue 7224

Change-Id: I36cc569c2926aa59ee7375e719b917d6d3681a43
Review-Link: https://gwt-review.googlesource.com/#/c/4323/
Let IE9+ use FocusImpl instead of IE6 version

fixes issue 8383

Change-Id: I082dfed75c54e2d90843f1b6a9eb8ac2f93d8fff
Change Generator.getAccessedPropertyNames() return type to Set<String>

Generator is a public API class and we don't want to encourage end
users to need to import from com.google.gwt.thirdparty.guava, so we
need to define the API around Set instead of ImmutableSet.

Also, remove the overload in InlineClientBundleGenerator.

Change-Id: I11741a8c1e0dccd3f2ac2dae68455aee7441dba5
Added support for deploying snapshots to maven repositories.

Note that this still does not support deploying snapshots locally.

Change-Id: Iab382becde1fdcb9a505937c7862ce1a3f937035
GWTify name and URLs in POM files

Change-Id: I66ce016d1b136bd1fbc25695585eecab15639ca2
Make method calls on null JSOs throw a NPE in DevMode.

Change-Id: If31642448f71704801b8fbe2c7387e5ddd4a80bc
Fix scalb to work with a scaleFactor of >=31 or <=-31.

The existing implementation uses an integer shift, which produces a
value of 0 for large shifts.

Change-Id: I36594ad83541a0869139b11da28485908080e0f2
Review-Link: https://gwt-review.googlesource.com/#/c/5322/
Set SO_REUSEADDR when starting Jetty

SO_REUSEADDR allows us to listen on TCP ports that are still in
TIME_WAIT status (i.e., someone else recently finished using it),
which is necessary for busy testing environments where many (or even
all) ephemeral TCP ports may be in this state.

The original comment says SO_REUSEADDR was disabled to prevent sharing
a port with another process.  However, it's actually SO_REUSEPORT that
allows multiple processes to listen on the same port.

Change-Id: Iafce162ef0398b7c935491a37a1b02cb0e48dfd8
Remove extra try catch for IE6/7 in entry function

According to comment and commit log this looks safe to remove:
https://code.google.com/p/google-web-toolkit/source/detail?r=7315

In general: We should avoid uncessary try catch clauses since
JavaScript JITs will not optimize such methods.

Change-Id: I45e73a800427afedc7fd5acd4dd06f40372aac40