The SNAPSHOT dependency is refetched, on a developer's machine or it is updated in every build. Whenever an agent deploys the artifact, it is updated in the shared repository. Note that the SNAPSHOT changes constantly. SNAPSHOT version references enable Maven to fetch the most recently deployed instance of the SNAPSHOT dependency at a dependent project build time. In a continuous integration environment, the SNAPSHOT version plays a vital role in keeping the integration build up-to-date while minimizing the amount of rebuilding that is required for each integration step. If a version number is followed by -SNAPSHOT, then Maven considers it the "as-yet-unreleased" version of the associated MajorVersion, MinorVersion, or IncrementalVersion. Maven treats the SNAPSHOT qualifier differently from all others. See Section 7.3 for information about version changes. Version resolution is also very important if you intend to use version ranges in your dependency references. Given the preceding example sequence, if your current reference was 1.0.10.2, then the plug-in would report 1.0.9.3 as a newer release. If Maven incorrectly identifies a newer release, then it is also reported incorrectly in the plug-in. When you are coordinating a large release, this goal can help you to find stale references in dependency configuration. The versions:dependency-updates-report goal examines a project's dependency hierarchy and reports which ones have newer releases available. One useful goal is versions:dependency-updates-report. The Maven Versions plug-in provides goals to check your project dependencies for currency in a different ways. 3) forced Maven to evaluate the version as a string.Īn example of this effect on Maven is found in the Maven Versions plug-in. Version 1.0.9.3 should come before 1.0.10.1 and 1.0.10.2, but the unexpected fourth field (. Because basic string comparison is performed on nonstandard versions, version comparison calculates the order of versions incorrectly in some cases.įor example, Maven arranges the version list in the following manner:
If you use a nonstandard versioning scheme, Maven release and version plug-in goals might not yield the expected results. Maven and its core plug-ins use version comparison for a number of tasks, most importantly, the release process. If you do not follow Maven versioning standards in your project versioning scheme, then for version comparison, Maven interprets the entire version as a simple string. Identical versions with different qualifier fields are compared by using basic string comparison. Maven's versioning scheme uses the following standards:Īll versions with a qualifier are older than the same version without a qualifier (release version).
0 kommentar(er)
