To get the final release, the code will go through several stages when key functions are implemented.
Once all the new features are implemented, then the code will usually go through the various stages of the preliminary version, such as beta versions and release candidates. When everyone is happy, the final version will be released and the whole process will start again.
In Spring Earth, the process goes:
Mx for Milestone sequentially numbered releaseRCx for release candidate sequentially numberedGA for General Availability - Final
For more on the various types, see this other SO answer .
The OP asks: why do I need a repository plugin?
The Spring Milestone repository is now the standard Maven repo plugin, or otherwise not really a big deal.
This policy in Spring publishes releases to the general public for those interested in testing them. Nearly all of the binary Java artifact publishing is in Maven these days. Therefore, these steps are published to the Maven repository.
To make it clear that these milestone releases should not be used in production code, they are published in a separate repo, not in Maven Central. Basically, do not use milestones unless you know what you are doing. And wait for the mistakes.
For more information on how Spring manages its repositories, take a look at Spring repository FAQs.
Boris the Spider
source share