build.gradle - Issue 29379647: Issue 4948 - add possibility to not send data depending on connection properties

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments.

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line
<Enter> :	respond to / edit current comment
d :	mark current comment as done

	Issue
u :	up to list of issues
m :	publish + mail comments
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue
# :	close issue

	Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :	save comment
<Esc> :	cancel edit

Side by Side Diff: build.gradle

Issue 29379647: Issue 4948 - add possibility to not send data depending on connection properties (Closed)

Patch Set: migrated from FilterEngine* to FilterEnginePtr*, minor improvements Created March 15, 2017, 12:48 p.m.

Left:
Right:

Use n/p to move between diff chunks; N/P to move between comments.

Jump to:

OLD	NEW
1 buildscript {	1 buildscript {

2 repositories {	2 repositories {

3 mavenLocal()	3 mavenLocal()

4 mavenCentral()	4 mavenCentral()

5 jcenter()	5 jcenter()

6 }	6 }

7 dependencies {	7 dependencies {

8 classpath 'com.android.tools.build:gradle:2.2.0'	8 classpath 'com.android.tools.build:gradle:2.3.0'
	sergei 2017/03/15 13:41:47 I don't know you policies but should not it be in I don't know you policies but should not it be in another commit? anton 2017/03/15 13:57:25 yes, it should. i will fix it Show quoted text On 2017/03/15 13:41:47, sergei wrote: > I don't know you policies but should not it be in another commit? yes, it should. i will fix it
9 }	9 }

10 }	10 }

11	11

12 subprojects {	12 subprojects {

13 task listAllDependencies(type: DependencyReportTask) {}	13 task listAllDependencies(type: DependencyReportTask) {}

14 }	14 }

OLD	NEW