forked from mojohaus/versions
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.apt
174 lines (118 loc) · 9.16 KB
/
index.apt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
~~ Licensed to the Apache Software Foundation (ASF) under one
~~ or more contributor license agreements. See the NOTICE file
~~ distributed with this work for additional information
~~ regarding copyright ownership. The ASF licenses this file
~~ to you under the Apache License, Version 2.0 (the
~~ "License"); you may not use this file except in compliance
~~ with the License. You may obtain a copy of the License at
~~
~~ http://www.apache.org/licenses/LICENSE-2.0
~~
~~ Unless required by applicable law or agreed to in writing,
~~ software distributed under the License is distributed on an
~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
~~ KIND, either express or implied. See the License for the
~~ specific language governing permissions and limitations
~~ under the License.
------
Introduction
------
Stephen Connolly
------
2009-04-21
------
Versions Maven Plugin
The Versions Plugin is used when you want to manage the versions of artifacts in a project's POM.
* Goals Overview
The Versions Plugin has the following goals.
* {{{./compare-dependencies-mojo.html}versions:compare-dependencies}} compares the dependency versions of the current
project to the dependency management section of a remote project.
* {{{./display-dependency-updates-mojo.html}versions:display-dependency-updates}} scans a project's dependencies and
produces a report of those dependencies which have newer versions available.
* {{{./display-plugin-updates-mojo.html}versions:display-plugin-updates}} scans a project's plugins and produces a
report of those plugins which have newer versions available, taking care of Maven version prerequisites.
* {{{./display-property-updates-mojo.html}versions:display-property-updates}} scans a project and produces a report of
those properties which are used to control artifact versions and which properties have newer versions available.
* {{{./update-parent-mojo.html}versions:update-parent}} updates the parent section of a project so that it references the
newest available version. For example, if you use a corporate root POM, this goal can be helpful if you need
to ensure you are using the latest version of the corporate root POM.
* {{{./update-properties-mojo.html}versions:update-properties}} updates properties defined in a project so that they
correspond to the latest available version of specific dependencies. This can be useful if a suite of dependencies
must all be locked to one version.
* {{{./update-property-mojo.html}versions:update-property}} Sets a property to the latest version in a given range of
associated artifacts.
* {{{./update-child-modules-mojo.html}versions:update-child-modules}} updates the parent section of the child modules
of a project so the version matches the version of the current project. For example, if you have an aggregator pom
that is also the parent for the projects that it aggregates and the children and parent versions get out of sync, this
mojo can help fix the versions of the child modules. (Note you may need to invoke Maven with the -N option in order to
run this goal if your project is broken so badly that it cannot build because of the version mis-match).
* {{{./lock-snapshots-mojo.html}versions:lock-snapshots}} searches the pom for all -SNAPSHOT versions and replaces them
with the current timestamp version of that -SNAPSHOT, e.g. -20090327.172306-4
* {{{./unlock-snapshots-mojo.html}versions:unlock-snapshots}} searches the pom for all timestamp locked snapshot versions
and replaces them with -SNAPSHOT.
* {{{./resolve-ranges-mojo.html}versions:resolve-ranges}} finds dependencies using version ranges and resolves the range
to the specific version being used.
* {{{./set-mojo.html}versions:set}} can be used to set the project version from the command line.
* {{{./set-property-mojo.html}versions:set-property}} can be used to set one or multiple properties to a given version from the command line.
* {{{./use-releases-mojo.html}versions:use-releases}} searches the pom for all -SNAPSHOT versions which have been
released and replaces them with the corresponding release version.
* {{{./use-next-releases-mojo.html}versions:use-next-releases}} searches the pom for all non-SNAPSHOT versions which
have been a newer release and replaces them with the next release version.
* {{{./use-latest-releases-mojo.html}versions:use-latest-releases}} searches the pom for all non-SNAPSHOT versions which
have been a newer release and replaces them with the latest release version.
* {{{./use-next-snapshots-mojo.html}versions:use-next-snapshots}} searches the pom for all non-SNAPSHOT versions which
have been a newer -SNAPSHOT version and replaces them with the next -SNAPSHOT version.
* {{{./use-latest-snapshots-mojo.html}versions:use-latest-snapshots}} searches the pom for all non-SNAPSHOT versions
which have been a newer -SNAPSHOT version and replaces them with the latest -SNAPSHOT version.
* {{{./use-next-versions-mojo.html}versions:use-next-versions}} searches the pom for all versions which
have been a newer version and replaces them with the next version.
* {{{./use-latest-versions-mojo.html}versions:use-latest-versions}} searches the pom for all versions which
have been a newer version and replaces them with the latest version.
* {{{./use-dep-version-mojo.html}versions:use-dep-version}} updates a dependency to a specific version.
* {{{./commit-mojo.html}versions:commit}} removes the <<<pom.xml.versionsBackup>>> files. Forms one half of the
built-in "Poor Man's SCM".
* {{{./revert-mojo.html}versions:revert}} restores the <<<pom.xml>>> files from the <<<pom.xml.versionsBackup>>> files.
Forms one half of the built-in "Poor Man's SCM".
* Reporting goals overview
The Versions Plugin has the following reporting goals.
* {{{./dependency-updates-report-mojo.html}versions:dependency-updates-report}} produces a report of those
project dependencies which have newer versions available.
* {{{./plugin-updates-report-mojo.html}versions:plugin-updates-report}} produces a report of those plugins which have
newer versions available.
* {{{./property-updates-report-mojo.html}versions:property-updates-report}} produces a report of
those properties which are used to control artifact versions and which properties have newer versions available.
* {{{./parent-updates-report-mojo.html}versions:parent-updates-report}} produces a report on possible parent artifact
upgrades.
* Usage
General instructions on how to use the Versions Plugin can be found on the {{{./usage.html}usage page}}. Some more
specific use cases are described in the examples given below. Last but not least, users occasionally contribute
additional examples, tips or errata to the
{{{http://docs.codehaus.org/display/MAVENUSER/Versions+Plugin}plugin's wiki page}}.
In case you still have questions regarding the plugin's usage, please have a look at the {{{./faq.html}FAQ}} and feel
free to contact the {{{./mail-lists.html}user mailing list}}. The posts to the mailing list are archived and could
already contain the answer to your question as part of an older thread. Hence, it is also worth browsing/searching
the {{{./mail-lists.html}mail archive}}.
If you feel like the plugin is missing a feature or has a defect, you can fill a feature request or bug report in our
{{{./issue-tracking.html}issue tracker}}. When creating a new issue, please provide a comprehensive description of your
concern. Especially for fixing bugs it is crucial that the developers can reproduce your problem. For this reason,
entire debug logs, POMs or most preferably little demo projects attached to the issue are very much appreciated.
Of course, patches are welcome, too. Contributors can check out the project from our
{{{./source-repository.html}source repository}} and will find supplementary information in the
{{{http://maven.apache.org/guides/development/guide-helping.html}guide to helping with Maven}}.
* Examples
To provide you with better understanding of some usages of the Plugin Name,
you can take a look into the following examples:
* {{{./examples/advancing-dependency-versions.html}Advancing dependency versions}}
* {{{./examples/compare-dependencies.html}Compare project dependencies to a remote project}}
* {{{./examples/display-dependency-updates.html}Checking for new dependency updates}}
* {{{./examples/display-plugin-updates.html}Checking for new plugin updates}}
* {{{./examples/display-property-updates.html}Checking for new property-linked updates}}
* {{{./examples/update-parent.html}Updating the Parent version}}
* {{{./examples/update-properties.html}Updating a version specified in a property}}
* {{{./examples/update-child-modules.html}Fixing a multi-module build}}
* {{{./examples/resolve-ranges.html}Resolve version ranges}}
* {{{./examples/lock-snapshots.html}Locking snapshot dependencies}}
* {{{./examples/unlock-snapshots.html}Unlocking snapshot dependencies}}
* {{{./examples/use-releases.html}Replacing -SNAPSHOT versions with their corresponding releases}}
* {{{./examples/set.html}Changing the project version}}
* {{{./examples/recording-changes.html}Recording version changes}}