MAVEN Development for version management

1.RELEASE version: If the version already exists in the local repository, the latest version of the is not downloaded from the MAVEN.

Version 2.SNAPSHOT: The latest version is downloaded based on the timestamp.

The version naming rule describes the:< component >-version number. jar

such as:Hollybeacon-basic-1.1.0.release.jar

Hollybeacon-message-1.0-snapshot.jar

Naming rules for version numbers:

official version:< large version >.< medium version >.< minor version;. RELEASE

Snapshot version:< large version >.< medium version >.< iteration >-snapshot

To illustrate:

1.1.0.RELEASE: < Large version >.< medium version >.< minor version;. RELEASE

< large version > update cycle of about one year, with very large code features or structural adjustments when using a large version

< in version > update cycle around one months, major when new features are added when using the version

< minor version > update Cycle in a week or so, mainly with minor bug fixes and feature additions.

Features of each version:

Release represents a tested official release, with fewer bugs.

SNAPSHOT represents a fast iteration of the development in the version, the test is small, there may be bugs, but the update frequency is fast, can be updated several hours.

MAVEN Development for version management