Author: buildbot
Date: Thu Nov 23 10:57:41 2017
New Revision: 1021248
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/main.pageCache
websites/production/cxf/content/release-management.html
Modified: websites/production/cxf/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/release-management.html
==============================================================================
--- websites/production/cxf/content/release-management.html (original)
+++ websites/production/cxf/content/release-management.html Thu Nov 23 10:57:41
2017
@@ -32,8 +32,8 @@
<link type="text/css" rel="stylesheet"
href="/resources/highlighter/styles/shThemeCXF.css">
<script src='/resources/highlighter/scripts/shCore.js'></script>
-<script src='/resources/highlighter/scripts/shBrushBash.js'></script>
<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
+<script src='/resources/highlighter/scripts/shBrushBash.js'></script>
<script>
SyntaxHighlighter.defaults['toolbar'] = false;
SyntaxHighlighter.all();
@@ -119,8 +119,8 @@ Apache CXF -- Release Management
...
</pre>
</div></div></div></div><p>Then, to actually perform the release, run the
below commands.</p><div class="preformatted panel" style="border-width:
1px;"><div class="preformattedContent panelContent">
-<pre>mvn release:prepare -Peverything,jaxws22
-mvn release:perform -Peverything,jaxws22
+<pre>mvn release:prepare -Peverything
+mvn release:perform -Peverything
</pre>
</div></div><div class="confluence-information-macro
confluence-information-macro-warning"><span class="aui-icon aui-icon-small
aui-iconfont-error confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>If you are performing the release
on a Mac, it is advisable to add -DpushChanges=false to the "release:prepare"
step above. The version of git that Apple ships with some versions of OSX has
problems pushing the changes in quick succession from the release plugin and
can become corrupt. Having the release plugin NOT push the changes and then
running "git push -tags origin master" works around that
problem.</p></div></div><div class="confluence-information-macro
confluence-information-macro-warning"><span class="aui-icon aui-icon-small
aui-iconfont-error confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>It is recommended to name the
local maintenance branches the same as the remote ones ("2.7.x-fixes", "3.0.x
-fixes", ...) to avoid issue with the branch names when running the release
plugin.</p></div></div><p> </p><p>The above commands tag the release,
update the poms versions, etc., then build it (off the tag), gpg sign and
deploy everything (including source jars and javadoc jars) to the <a
shape="rect" class="external-link" href="https://repository.apache.org";>Nexus
repository location</a>. When the build is done staging, you next need to login
to the Nexus repository and "close" the staging area (click on Staging
Repositories in the left-side menu, select the repo you just uploaded and then
select the close button.) Closing is very important. After the staging area is
closed, note the URL for the staging area as you will need that for the
vote.</p><p>At this point, everything "pre-vote" is done. Call the vote.</p><h2
id="ReleaseManagement-Releasingtheartifacts">Releasing the
artifacts</h2><ul><li>Maven artifacts - After the vote passes, you'll need to
promote that staging reposi
tory to the main location. Login to <a shape="rect" class="external-link"
href="https://repository.apache.org";>Nexus repository location</a> to do that
as well, find the staging repository and click the Release
button.</li></ul><ul><li><p>Distributions - You will need to commit the
distributions into the special svn distribution area: <a shape="rect"
class="external-link"
href="https://dist.apache.org/repos/dist/release/cxf";>https://dist.apache.org/repos/dist/release/cxf</a>
<br clear="none"> after you commit they will be live on dist.apache.org fairly
quickly, but it will still take time for the mirrors to get copies. It's likely
easier to make the directory via an svn command, check out just that directory,
and then add the files. The dist area is rather large (400MB or so) so checking
out the entire thing may be slow.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="brush: java; gutter: false; theme: Default"
style="font-size:12px;">svn mkdir
https://dist.apache.org/repos/dist/release/cxf/2.6.3
