Author: buildbot
Date: Tue Mar 3 14:36:45 2020
New Revision: 1057318
Log:
Staging update by buildbot for felix
Modified:
websites/staging/felix/trunk/content/ (props changed)
websites/staging/felix/trunk/content/documentation/development/release-management-nexus.html
Propchange: websites/staging/felix/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Mar 3 14:36:45 2020
@@ -1 +1 @@
-1874727
+1874728
Modified:
websites/staging/felix/trunk/content/documentation/development/release-management-nexus.html
==============================================================================
---
websites/staging/felix/trunk/content/documentation/development/release-management-nexus.html
(original)
+++
websites/staging/felix/trunk/content/documentation/development/release-management-nexus.html
Tue Mar 3 14:36:45 2020
@@ -116,7 +116,6 @@ In this case please ask a member of the
<ul>
<li>each and every release must be <a
href="https://www.apache.org/dev/release-signing.html";>SIGNED</a>; your public
key should be added to [https://www.apache.org/dist/felix/KEYS] (see
<em>Appendix A</em>)</li>
<li>your public key should also be cross-signed by other Apache committers
(not required, but suggested)</li>
-<li>when preparing the release on Mac OS X, make sure you read <em>Appendix
B</em> before continuing</li>
<li>make sure you have all Apache servers defined in your <a
href="https://maven.apache.org/developers/committer-settings.html";>settings.xml</a></li>
<li>use Maven 3.5.0 (or higher) </li>
</ul>
@@ -178,7 +177,7 @@ the released version.
</li>
<li>Stage the release for a vote
<div class="codehilite"><code>$ mvn release:perform</code></div><ul>
-<li>the release will automatically be inserted into a temporary staging
repository for you, see the Nexus <a
href="http://www.sonatype.com/books/nexus-book/reference/staging.html";>staging
documentation</a> for full details</li>
+<li>the release will automatically be inserted into a temporary staging
repository for you, see the Nexus <a
href="https://www.sonatype.com/books/nexus-book/reference/staging.html";>staging
documentation</a> for full details</li>
<li>you can continue to use <code>mvn release:prepare</code> and <code>mvn
release:perform</code> on other sub-projects as necessary on the same machine
and they will be combined in the same staging repository - this is useful when
making a release of the Felix framework and its associated bundles.</li>
</ul>
</li>
@@ -200,10 +199,10 @@ Subject: [VOTE] Release Felix XXX versio
Hi,
We solved N issues in this release:
-http://issues.apache.org/jira/...
+https://issues.apache.org/jira/...
There are still some outstanding issues:
-http://issues.apache.org/jira/...
+https://issues.apache.org/jira/...
Staging repository:
https://repository.apache.org/content/repositories/orgapachefelix-[YOUR
REPOSITORY ID]/
@@ -274,7 +273,7 @@ If you are not a member of the Apache Fe
the PMC to execute this step.
</div>
-<p>We use the distribution mechanism as described in <a
href="http://www.apache.org/dev/release.html#upload-ci";>How do I upload a
release (newer way)?</a></p>
+<p>We use the distribution mechanism as described in <a
href="https://www.apache.org/dev/release.html#upload-ci";>How do I upload a
release (newer way)?</a></p>
<ol>
<li>Check out the <a
href="https://dist.apache.org/repos/dist/release/felix";>Felix releases
repository</a>;</li>
<li><code>svn add</code> the artifacts to your checkout;</li>
@@ -283,7 +282,7 @@ will remove the artifacts from the main
are still kept in the archive;</li>
<li><code>svn commit</code> your changes.</li>
</ol>
-<p>After committing your changes, the <a
href="http://www.apache.org/dist/felix";>Apache Felix Dist</a>
+<p>After committing your changes, the <a
href="https://www.apache.org/dist/felix";>Apache Felix Dist</a>
folder is immediately updated. Updating the mirrors takes another few hours
(up to a day).</p>
<h3 id="release-to-the-maven-repository">Release to the Maven Repository<a
class="headerlink" href="#release-to-the-maven-repository" title="Permanent
link">¶</a></h3>
@@ -302,7 +301,7 @@ in a checkout of the release tag (target
<span class="nv">$ </span><span class="nb">export </span><span
class="nv">obr</span><span class="o">=</span><span class="k">${</span><span
class="nv">site</span><span class="k">}</span>/obr
<span class="nv">$ </span>mvn clean install <span class="se">\</span>
org.apache.felix:maven-bundle-plugin:deploy <span class="se">\</span>
- -DprefixUrl<span class="o">=</span>http://repo1.maven.org/maven2 <span
class="se">\</span>
+ -DprefixUrl<span class="o">=</span>https://repo1.maven.org/maven2 <span
class="se">\</span>
-DremoteOBR<span class="o">=</span>releases.xml <span class="se">\</span>
-DaltDeploymentRepository<span
class="o">=</span>apache.website::default::file:///<span
class="k">${</span><span class="nv">obr</span><span class="k">}</span>
<span class="nv">$ </span>svn commit -m<span class="s2">"..."</span>
<span class="k">${</span><span class="nv">obr</span><span
class="k">}</span>/repository.xml
@@ -311,7 +310,7 @@ in a checkout of the release tag (target
<p>After committing the site must be published. If you release to OBR before
<a href="update-the-site">updating the site</a> you can defer publishing until
after that.
Otherwise publish the site by visiting the <a
href="https://cms.apache.org/felix/publish";>Site Publication</a> link.</p>
-<p>The <a href="http://felix.apache.org/obr/releases.xml";>releases</a> page is
updated immediately.</p>
+<p>The <a href="https://felix.apache.org/obr/releases.xml";>releases</a> page
is updated immediately.</p>
<p><strong>Note</strong>: the project building the bundle must use the <a
href=""></a> and use a version equal to or higher than 1.4.2.</p>
<p><strong>Note</strong>: with Maven 3, you must add an extension to your
<code><build></code> providing the SCP/SSH protocol:</p>
<div class="codehilite"><pre><span class="nt"><build></span>
@@ -340,7 +339,7 @@ Otherwise publish the site by visiting t
<h2 id="publish-generated-documentation">Publish Generated Documentation<a
class="headerlink" href="#publish-generated-documentation" title="Permanent
link">¶</a></h2>
<p>This procedure applies currently only to the
<code>maven-bundle-plugin</code>:</p>
<ol>
-<li>Checkout the release tag of the plugin (or reset your svn workspace to the
release tag)</li>
+<li>Checkout the release tag of the plugin </li>
<li>Run <code>mvn clean package site</code></li>
<li>Create a new folder for the new version at
<code>https://svn.apache.org/repos/asf/felix/site/trunk/content/components/bundle-plugin-archives/bundle-plugin-<version></code>
and publish the generated site from <code>target/site</code> there</li>
<li>Remove the previous documentation from
<code>components/bundle-plugin</code> and SVN-copy the new version there as
well</li>
@@ -353,9 +352,9 @@ The Felix team is pleased to announce th
<<insert short description of the sub-project>>
- http://felix.apache.org/site/apache-felix-XXX.html
+ https://felix.apache.org/site/apache-felix-XXX.html
-This release is available from http://felix.apache.org/site/downloads.cgi and
Maven:
+This release is available from https://felix.apache.org/site/downloads.cgi and
Maven:
<dependency>
<groupId>org.apache.felix</groupId>
@@ -375,7 +374,7 @@ Enjoy!
<p>Remember to forward this announcement to
<code>[email protected]</code> - try <em>not</em> to cross-post (CC:)
announcements to both user and dev lists.</p>
<p><em>Remind Carsten about this release when he writes the next board report
;)</em></p>
-<h2
id="appendix-a-create-and-add-your-key-to-httpwwwapacheorgdistfelixkeys">Appendix
A: create and add your key to http://www.apache.org/dist/felix/KEYS<a
class="headerlink"
href="#appendix-a-create-and-add-your-key-to-httpwwwapacheorgdistfelixkeys"
title="Permanent link">¶</a></h2>
+<h2
id="appendix-a-create-and-add-your-key-to-httpswwwapacheorgdistfelixkeys">Appendix
A: create and add your key to https://www.apache.org/dist/felix/KEYS<a
class="headerlink"
href="#appendix-a-create-and-add-your-key-to-httpswwwapacheorgdistfelixkeys"
title="Permanent link">¶</a></h2>
<p>If you are using a *nix system with a working OpenSSH, GnuPG, and bash you
can create and add your own key with the following command:</p>
<div class="codehilite"><pre><span class="nv">$ </span>gpg --gen-key
</pre></div>
@@ -399,25 +398,9 @@ dist release repository (you also need t
</pre></div>
-<p>You are now <em>DONE</em> and the changes are visible on
http://www.apache.org/dist/felix/KEYS.</p>
-<h2 id="appendix-b-preparing-releases-on-mac-os-x">Appendix B: preparing
releases on Mac OS X<a class="headerlink"
href="#appendix-b-preparing-releases-on-mac-os-x" title="Permanent
link">¶</a></h2>
-<p>When running the <code>mvn release:prepare</code> command on Mac OS X, you
might see the following error:</p>
-<div class="codehilite"><pre>[INFO] Working directory:
/homedir/dev/felix/dependencymanager
-[INFO] ------------------------------------------------------------------------
-[ERROR] BUILD FAILURE
-[INFO] ------------------------------------------------------------------------
-[INFO] Unable to commit files
-Provider message:
-The svn command failed.
-Command output:
-svn: Commit failed (details follow):
-svn: MKACTIVITY of
'/repos/asf/!svn/act/4f11ad5d-9161-0410-b4dd-cb727141ea8c':
authorization failed (https://svn.apache.org){code}
-</pre></div>
-
-
-<p>This is due to a bug in Subversion on the Mac, as described by Brett Porter
in his
[blog|http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/].
He proposes putting an "svn" script at the head of your path to fix the
issue.</p>
+<p>You are now <em>DONE</em> and the changes are visible on
https://www.apache.org/dist/felix/KEYS.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1874727 by cziegeler on Tue, 3 Mar 2020 14:26:27 +0000
+ Rev. 1874728 by cziegeler on Tue, 3 Mar 2020 14:36:27 +0000
</div>
<div class="trademarkFooter">
Apache Felix, Felix, Apache, the Apache feather logo, and the Apache
Felix project
