Before starting with dependency configuration, let's discuss how to publish packaged software in Java. You package and publish either in .jar or .war or .ear file formats to a repository. The goal is to share these assets within the teams in an organization or with open source developers. Consider a scenario where you are publishing a utility project (messageutil.jar) to a repository. Although the publication process mostly depends on an organization's policy, the common practice is, all the assets that you plan to publish should be versioned and stored in a central repository, so that all other teams can share it. This versioning helps to track different versions of libraries. With versioned libraries, you can also revert to old versions in case of any functionality issues. Whenever you publish any asset to the repositories, always make sure it is versioned. To know more about versioning look at this link: http://semver.org/.