History log of /frameworks/data-binding/compilationTests/src/test/resources/module_build.gradle
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
9784c9aaedeb863018f5fcaa0a598e8e2f8ed2f3 13-Oct-2015 Yigit Boyar <yboyar@google.com> Data binding as studio dep + java6

This CL gets rid of the gradle plugin and instead provides
DataBindingBuilder for the gradle plugin to directly use.

Now, everything that is deployed via SDK Manager (lib and adapters)
are included as prebuilts so that we avoid accidently changing
them w/o an SDK manager release.

There is still work to do:
> re-enable proguard for externel dependencies
> release a batch to ensure everything works

Bug: 22516688
Change-Id: I83ace15bd6d3d23bf5b4ad850f36453dd23ebd43
/frameworks/data-binding/compilationTests/src/test/resources/module_build.gradle
7d9836f8bd4f2525597b091787d0858784c6c22e 14-Sep-2015 Yigit Boyar <yboyar@google.com> Move tool versions into config

Change-Id: Ia75eb20a50571aa6f8ebb80596962694d2d535fa
/frameworks/data-binding/compilationTests/src/test/resources/module_build.gradle
8b1da958f181639d33dfaa907c0ee66add2decd6 23-Jun-2015 Yigit Boyar <yboyar@google.com> Don't generate inflators for libraries

If a library project (A) depends on anohter library project (B),
we would generate code that accesses R file of project B while
compiling project A. Unfortunately, gradle does not generate that
R file when compiling A, it only exists when compiling the app
and B.
This CL changes the base class generation to not to generate
real code for base classes unless we are building the final app.

Bug: 22001270
Change-Id: Ic107001ab58c94016f37f7f6fc0470a822db3aa7
/frameworks/data-binding/compilationTests/src/test/resources/module_build.gradle