|
15 | 15 | See the License for the specific language governing permissions and |
16 | 16 | limitations under the License. |
17 | 17 | --> |
18 | | -<document> |
19 | | - |
| 18 | +<document xmlns="http://maven.apache.org/XDOC/2.0" |
| 19 | + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
| 20 | + xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 https://maven.apache.org/xsd/xdoc-2.0.xsd"> |
20 | 21 | <properties> |
21 | 22 | <title>Overview</title> |
22 | 23 | < author email= "[email protected]">Apache Commons Team</ author> |
|
49 | 50 | <p> |
50 | 51 | Available Goals (which are meant to be used together; the only reason they are separated is for |
51 | 52 | code readability): |
| 53 | + </p> |
52 | 54 | <ul> |
53 | 55 | <li> |
54 | 56 | <b>commons-release:detach-distributions</b> - Remove |
|
65 | 67 | <a href="vote-txt.html">commons-release:vote-txt</a> -Dcommons.nexus.repo.id=nnnn [-Dgit.tag.name] # where nnn is the number following orgapachecommons- in the Nexus 'Repository' column |
66 | 68 | </li> |
67 | 69 | </ul> |
68 | | - </p> |
69 | 70 | </section> |
70 | 71 |
|
71 | 72 | <section name="Using the plugin"> |
|
143 | 144 | After the above configuration performing the release would occur by (<i>note.</i> more |
144 | 145 | in depth details can be found at |
145 | 146 | <a href="https://commons.apache.org/releases/prepare.html">Preparations For A Release</a>): |
146 | | - <ol> |
147 | | - <li>creating our release branch,</li> |
148 | | - <li>checking compatibility,</li> |
149 | | - <li>checking your dependencies,</li> |
150 | | - <li>checking javadocs and code style,</li> |
151 | | - <li>checking the apache license,</li> |
152 | | - <li>configure the build to generate a complete set of release artifacts,</li> |
153 | | - <li>preparing the release notes, updating the download file and other autogenerated files,</li> |
154 | | - <li>tagging the release candidate, and</li> |
155 | | - <li> |
| 147 | + </p> |
| 148 | + <ol> |
| 149 | + <li>creating our release branch,</li> |
| 150 | + <li>checking compatibility,</li> |
| 151 | + <li>checking your dependencies,</li> |
| 152 | + <li>checking javadocs and code style,</li> |
| 153 | + <li>checking the apache license,</li> |
| 154 | + <li>configure the build to generate a complete set of release artifacts,</li> |
| 155 | + <li>preparing the release notes, updating the download file and other autogenerated files,</li> |
| 156 | + <li>tagging the release candidate, and</li> |
| 157 | + <li> |
156 | 158 | running the following command: |
157 | 159 | <source><![CDATA[ |
158 | 160 | mvn -Duser.name=<yourApacheId> [-Duser.password=<yourApacheIdsPassword] [-Dcommons.release.dryRun=true -Ptest-deploy] -Prelease clean test site deploy |
159 | | -]]></source> |
160 | | - </li> |
161 | | - </ol> |
| 161 | +]]></source></li> |
| 162 | + </ol> |
| 163 | + <p> |
162 | 164 | To avoid specifying distribution credentials at the command |
163 | 165 | line, consider using the <code>distServer</code> plugin configuration parameter (property <code>commons.distServer</code>) |
164 | 166 | to specify a server definition in Maven <code>settings.xml</code> which defines your (encrypted, right?) authentication info. |
165 | 167 | </p> |
166 | | - |
167 | 168 | <p> |
168 | 169 | If the component is new, then, before running this maven command, you would want to create |
169 | 170 | the requisite subversion directory <code>https://dist.apache.org/repos/dist/dev/commons/foo</code>. Notice, |
|
0 commit comments