| bdc7aa8269502b3fc3ce73c124e4f1b2092502c9 |
|
23-Oct-2015 |
George Mount <mount@google.com> |
Use a dynamically-generated class to relax requirement to upgrade.
We may need some static methods between releases and instead of
requiring a release, we can now supply the methods as a dynamically
generated class, DynamicUtil
Change-Id: I9d53ae99b4b5717cd4780efdcb7a3f85bfac8dd9
/frameworks/data-binding/gradlePlugin/src/main/java/android/databinding/tool/DataBindingExcludeGeneratedTask.java
|
| 08119ea342cb47910ca80ff646d746f00e4663ce |
|
06-Jul-2015 |
Yigit Boyar <yboyar@google.com> |
Print encoded errors only if data binding is invoked from the IDE
This CL makes Scope aware of execution environment. Now when invoked
from tests or via IDE, we'll print exceptions as encoded so that we
can parse them back. When user invokes from command line or any other
tool, we will print human readable errors.
The encoded error format may still change depending on conversations
w/ Studio team.
Bug: 21953001
Change-Id: I5bd3ea0cb6728e011225ee84d3e38817a2993a43
/frameworks/data-binding/gradlePlugin/src/main/java/android/databinding/tool/DataBindingExcludeGeneratedTask.java
|
| b6887f1479c3ecec38a7989748ef33de1fbcd973 |
|
12-Jun-2015 |
Yigit Boyar <yboyar@google.com> |
Export generated class list from javac
Previously, gradle plugin would figure out generated class names
that should be excluded from the packaging. This CL changes that
behavior to export the list from java compiler so that it is
consistent going forward.
This CL also changes exclusion task to always exclude generated
binding info class to not to leak any information about user's
local.
Bug: 21668472
Change-Id: Ibeed24bd854781942b4185f618a5cd1eafe706d3
/frameworks/data-binding/gradlePlugin/src/main/java/android/databinding/tool/DataBindingExcludeGeneratedTask.java
|