# Maintain Library Versions ACross Modules

DevFeed: [Maintain Library Versions ACross Modules](<https://devfeed.tech/articles/maintain-library-versions-across-modules-22821.md>)

Original publisher: [Read original article](<http://androidessence.com/maintain-library-versions-across-modules/>)

Author: Adam McNeilly

Published: 2017-05-05T00:00:00Z

Content type: tutorial

Language: en

Sources: [Android Essence](<https://devfeed.tech/sources/android-essence.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [modules](<https://devfeed.tech/topics/modules.md>), [Android](<https://devfeed.tech/topics/android.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [build-tools](<https://devfeed.tech/tags/build-tools.md>), [code](<https://devfeed.tech/tags/code.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [modules](<https://devfeed.tech/tags/modules.md>), [project](<https://devfeed.tech/tags/project.md>)

## AI overview

A tutorial on centralizing Android library and build configuration version numbers in the project-level Gradle file so they can be reused consistently across multiple modules.

## Source excerpt

It is tough enough maintaing your app by updating the support library version numbers every time a new version is out, let alone factoring in any other third party libraries you may use. This is especially painful if you have multiple modules, as you have to update the version in each build.gradle file. Thankfully, we can make use of the project level gradle file to make this more maintainable.