submodules/libadblockplus-android/libadblockplus-android/AndroidManifest.xml - Issue 29345540: Issue 4030 - Move JNI bindings into separate library project

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: submodules/libadblockplus-android/libadblockplus-android/AndroidManifest.xml

Issue 29345540: Issue 4030 - Move JNI bindings into separate library project (Closed)

Patch Set: Created June 3, 2016, 1:42 p.m.

Left:
Right:

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

Jump to:

OLD	NEW
(Empty)
	1 <?xml version="1.0" encoding="utf-8"?>

	2 <manifest xmlns:android="http://schemas.android.com/apk/res/android"

	3 package="org.adblockplus.libadblockplus"

	4 android:versionCode="359"

	5 android:versionName="1.3" >
	diegocarloslima 2016/09/06 01:05:49 Since libadblockplus-android will be an independen Since libadblockplus-android will be an independent project with its own releases, I think that we should do a fresh start to its versionCode/versionName (starting from 0.1 or 1.0) instead of using adblockplusandroid current version anton 2016/09/06 05:56:22 That makes sense, i'd prefer 1.0 since we have rel Show quoted text On 2016/09/06 01:05:49, diegocarloslima wrote: > Since libadblockplus-android will be an independent project with its own > releases, I think that we should do a fresh start to its versionCode/versionName > (starting from 0.1 or 1.0) instead of using adblockplusandroid current version That makes sense, i'd prefer 1.0 since we have released product (proxy app) that is using the library.
	6

	7 <uses-sdk

	8 android:minSdkVersion="9"

	9 android:targetSdkVersion="16" />

	10

	11 </manifest>

OLD	NEW