platform_external_dagger2/Android.mk, branch pie-release

Use USE_OPENJDK9 instead of EXPERIMENTAL_USE_OPENJDK9

2017-11-15T22:48:59+00:00

This avoids duplicating the semantics of an unset/empty
EXPERIMENTAL_USE_OPENJDK9.

Test: make showcommands core-oj (in environments with
      EXPERIMENTAL_USE_OPENJDK9 set to "", "1.8", and "true").
Bug: 38177295

Change-Id: Ic7b9fdaf8574a1478b4382a399e0f3c4cbc5435a

Move host dependencies to Android.bp

2017-09-11T20:05:44+00:00

Also move dagger2-inject-host to a static dependency, all users of
dagger2-host include dagger2-inject-host statically, and depending
on as non-static library causes it to be installed unnecessarily.

See build/soong/README.md for more information.

The libraries in lib/ are used outside the project by host tools
that are prerequisites for converting device modules to soong.

Test: m -j checkbuild
Change-Id: I3f8164c3a67b37f88fca888cabac290d2c927d1e

Update auto-value to version 1.4.1.

2017-07-17T17:45:49+00:00

I built these jars locally from the "auto" subdirecories of the
sources from [1], using maven 3.
Based on the version name, those should exactly equal the sources
browsable at [2], but this was not independently verified.

The commands used to build the .jars were:
 - For auto-value-1.4.1-sources.jar:  mvn source:jar
 - For auto-value-1.4.1.jar:          mvn install

auto-value-1.4.1.jar.txt is a copy of [3].

Bug: 63748235
Test: Treehugger

[1] https://github.com/google/auto/archive/auto-value-1.4.1.zip
[2] https://github.com/google/auto/tree/auto-value-1.4.1
[3] https://github.com/google/auto/blob/auto-value-1.4.1/LICENSE.txt

Change-Id: I3d85cbc9257c283873c2b424860169ebe4f16cea

Fix annotation processors working w/ generated code on OpenJDK 9 toolchain

2017-05-24T21:21:51+00:00

Generated code is annotated with @javax.annotation.Generated.
Annotation processors working with such code break on OpenJDK 9
toolchains because that class lives in the module
"java.xml.ws.annotation".

This CL makes that module available by adding the javac command
line flag
      -J--add-modules=java.xml.ws.annotation to javac
When the environment variable EXPERIMENTAL_USE_OPENJDK9 is set
to true.

Test: make ANDROID_COMPILE_WITH_JACK=false checkbuild tests \
      && make checkbuild tests
      (with OpenJDK 8u45 toolchain on the PATH)
Test: make EXPERIMENTAL_USE_OPENJDK9=true \
      ANDROID_COMPILE_WITH_JACK=false checkbuild
      (with jdk 9-ea+170 toolchain on the PATH)

Bug: 62050818
Change-Id: Ib3e19621a0e24f79807be0dd239e9abec3350383

Replace custom annotation processor handling

2017-04-07T23:30:34+00:00

Use LOCAL_ANNOTATION_PROCESSORS instead of custom annotation
processor handling.

Test: m -j java
Change-Id: Ia01cc51ea8dbe0842145789ef22a278573c1ee6b

Pin libraries needed by vogar tool to java 1.7

2016-02-23T16:59:42+00:00

vogar still uses javac/dx by default. dx does not
handle v52 class files. The default java version
is going to switch to 1.8. This change pins the
targets need by vogar to 1.7.

Bug: 26753820
Bug: 27310428
Change-Id: I0f18bc98d3500828a09dbe5a4766940ee993b9fe

Removed unnecessary disabling of Jack

2015-12-07T13:06:04+00:00

The annotation processor only works on host at the moment and as
Jack is not used for the host build disabling jack, using
  LOCAL_JAVA_ENABLED := disabled
is unnecessary so any references to it will be removed.

Change-Id: I950ae221173dfe6fa6ae98d73cda6b98dcf07943

Update dagger2 and improve build file

2015-11-26T13:58:41+00:00

Updates daggers2 to a later version, reverts change that adds a
dependency on Guava v19 as AOSP currently only has v18. See
README.android for more details.

Made a couple of changes to the build to make it reusable.

1) Added dagger2_annotation_processor.mk to define values that
are needed by modules that depend on dagger2.
2) Added java_annotation_processor.mk to do the magic needed to
make the annotation processors work properly.

Change-Id: Ie0e8b0e34c961f64ccd0a45bd93a7ea6a216ddf3

Use a -processor option per processor class

2015-11-24T16:11:12+00:00

The code indexing tool does not parse the value of the
-processor option as a comma separated list so use one class per
option.

Change-Id: I3fc1f953ca39fe1e5b00af6e7cc88cc38caa80f5

Work around limitation in code indexing tool

2015-11-24T14:36:05+00:00

A code indexing tool does not support the default discovery of
annotation processors or using the -classpath as the default
class path to search for annotation processor classes so they
both have to be specified explicitly using -processor and
-processorpath respectively.

At the moment this hard codes the path to an intermediate file,
this should be a temporary measure either until a better way of
building the -processorpath is found, -processorpath defaults
to -classpath, or until default discovery works properly.

Change-Id: I6224041972d1ef8d60fd153263bb0a1468114d03