Is versionCode / versionName required in the library manifest?

Below is the manifesto of one of my library projects. I am currently increasing versionCode and versionName with every change. It's necessary?

<?xml version="1.0" encoding="utf-8"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" android:installLocation="preferExternal" android:versionCode="14" android:versionName="1.1.7" package="com.tubala.android" > <uses-permission android:name="android.permission.INTERNET" /> <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" /> <uses-sdk android:minSdkVersion="7" android:targetSdkVersion="11" /> </manifest> 

Thanks in advance.

+6
source share
2 answers

Currently, the AndroidManifest.xml the Android library is completely ignored when creating an application using this library. The only aapt tool aapt is the package attribute (to generate the R-class into the correct package).

This may be changed in future releases. But I would say that you should still keep your version control. This is good practice (even if build tools ignore it).

+3
source

android:versionName attribute is not required. These are just version users who see when they open your application information in the application manager.

android:versionCode is more important. You must increase it every time you publish your application on the Android Market.

0
source

Source: https://habr.com/ru/post/897076/


All Articles