What is snapshot builds/sources version?
It is a development version that precedes the final release version. You can identify a snapshot version of a Maven package by the suffix SNAPSHOT that is appended to the package version. For example, the snapshot of version 1.1 is 1.1-SNAPSHOT .
The difference between a "real" version and a snapshot version is that snapshots might get updates. That means that downloading 1.0-SNAPSHOT today might give a different file than downloading it yesterday or tomorrow.
The snapshot builds are nothing but development builds. 2) Release builds: Release means removing the SNAPSHOT at the version ID for the build. These are the regular build versions. Snapshot artifacts and release artifacts are push to snapshot, release repositories respectively.
The snapshot repository is a repository used for incremental, unreleased artifact versions. A snapshot version is a version that has not yet been released. The general idea is to have a snapshot version before the released version.
Specific to JDK 7, snapshot releases are for users to download and review while the platform is still being developed.
http://www.oracle.com/technetwork/java/javase/downloads/ea-jsp-142245.html
As a general source control (version control) term, a snapshot version indicates a view of the source code taken at a specific time. This is not necessarily stable or ready for full use and can be changed in the future, as opposed to a release version which is stable and should be final.
That's another name for so-called daily build (or periodic build or nightly build). A script just builds all the sources periodically. This way anyone who is interested in the recent changes can have the almost freshest version every day. A tag is applied to the sources in the repository so that they can be later retrieved to reproduce the build - that forms "a snapshot" of the sources for that build.
Compare this to "official release" - it is carefully planned. Usually a separate branch is created in the repository where only necessary edits are committed. Then after the team decides it is good enough they run the build process, test it thoroughly and publish.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With