This is an automated email from the ASF dual-hosted git repository.
rombert pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new c410154 Update release management docs for IDE Tooling
c410154 is described below
commit c41015455eab7149d310f5c7bec0efa0b28e0de7
Author: Robert Munteanu <[email protected]>
AuthorDate: Mon Feb 26 23:55:15 2018 +0200
Update release management docs for IDE Tooling
---
documentation/bundles/org-apache-sling-junit-bundles.html | 4 ++--
documentation/development/release-management.html | 11 ++++++++---
2 files changed, 10 insertions(+), 5 deletions(-)
diff --git a/documentation/bundles/org-apache-sling-junit-bundles.html
b/documentation/bundles/org-apache-sling-junit-bundles.html
index 26fa038..83dc150 100644
--- a/documentation/bundles/org-apache-sling-junit-bundles.html
+++ b/documentation/bundles/org-apache-sling-junit-bundles.html
@@ -284,7 +284,7 @@ public final TeleporterRule teleporter =
<h4><a href="#launchpadcustomizer"
name="launchpadcustomizer">LaunchpadCustomizer</a></h4>
<p>The <em><a
href="https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/master/src/main/java/org/apache/sling/junit/teleporter/customizers/LaunchpadCustomizer.java";><code>LaunchpadCustomizer.java</code></a></em>
only verifies that a Sling instance is ready at a given port and configures
the <code>ClientSideTeleporter</code> to deploy to
<code>http://localhost:8080</code> with the credentials
<code>admin</code>:<code>admin</code>. <code>LaunchpadCustomizer</c [...]
<h4>BWIT_TeleporterCustomizer</h4>
-<p>The <em><a
href="https://github.com/apache/sling-samples/tree/master/testing/bundle-with-it/src/test/java/org/apache/sling/junit/teleporter/customizers/BWIT_TeleporterCustomizer.java";><code>BWIT_TeleporterCustomizer.java</code></a></em>
relies on <code>SlingTestBase</code> to set the server's base url and
credentials. Additionally the test bundle is adjusted so that the API is not
included in it (but rather referenced from another bundle). The bootstrapping
of the Sling instance is tw [...]
+<p>The <em><a
href="https://github.com/apache/sling-samples/tree/master/testing/bundle-with-it/src/test/java/org/apache/sling/junit/teleporter/customizers/BWIT_TeleporterCustomizer.java";><code>BWIT_TeleporterCustomizer.java</code></a></em>
relies on <code>SlingTestBase</code> to set the server's base url and
credentials. Additionally the test bundle is adjusted so that the API is not
included in it (but rather referenced from another bundle). The bootstrapping
of the Sling instance is tw [...]
<p>Those should give you an overview on what can be done with a customizer and
decide whether you need to write your own one or using the default customizer
is just enough.</p>
<h2><a
href="#org-apache-sling-junit-healthcheck-run-junit-tests-as-sling-health-checks"
name="org-apache-sling-junit-healthcheck-run-junit-tests-as-sling-health-checks">org.apache.sling.junit.healthcheck:
run JUnit tests as Sling Health Checks</a></h2>
<p>This bundle allows JUnit tests to run as <a
href="/documentation/bundles/sling-health-check-tool.html">Sling Health
Checks</a>, which can be useful when defining smoke tests for example, allowing
them to be used both at build time and run time.</p>
@@ -321,7 +321,7 @@ TEST_PASSED
<p>The <code>org.apache.sling.junit.remote</code> bundle provides utilities to
run server-side JUnit tests, but using the newer <code>TeleporterRule</code>
described above is much simpler. As a result, this bundle should only be needed
for existing tests that were written using its mechanisms.
</p></section></div></div>
<div class="footer">
<div class="revisionInfo">
- Last modified by <span class="author">Robert
Munteanu</span> on <span class="comment">Wed Nov 22 23:22:38 2017 +0200</span>
+ Last modified by <span class="author">Dan Klco</span> on
<span class="comment">Thu Feb 22 16:26:54 2018 -0500</span>
</div> <p>
Apache Sling, Sling, Apache, the Apache feather logo, and
the Apache Sling project logo are trademarks of The Apache Software Foundation.
All other marks mentioned may be trademarks or registered trademarks of their
respective owners.
</p><p>
diff --git a/documentation/development/release-management.html
b/documentation/development/release-management.html
index ee07d8a..ec1ca81 100644
--- a/documentation/development/release-management.html
+++ b/documentation/development/release-management.html
@@ -328,7 +328,12 @@ Enjoy!
<li><a
href="http://wiki.apache.org/incubator/SigningReleases";>http://wiki.apache.org/incubator/SigningReleases</a></li>
</ol>
<h2><a href="#releasing-the-sling-ide-tooling"
name="releasing-the-sling-ide-tooling">Releasing the Sling IDE Tooling</a></h2>
+<div class="note">Eclipse is very aggresive about caching artifacts with the
same coordinates. Make sure that once you build the artifacts
+with code signing enabled you install the right ones. If you install artifacts
with the same version but not signed, Eclipse will cache
+that version indefinitely with no known workaround except setting up a new
installation of Eclipse.</div>
<p>While the Sling IDE tooling is built using Maven, the toolchain that it is
based around does not cooperate well with the maven-release-plugin. As such,
the release preparation and execution are slightly different. Also note that we
sign release using the Symantec code signing service, see <a
href="https://reference.apache.org/pmc/codesigning";>Using the code signing
service </a> for details.</p>
+<div class="note">While we sort out a proper location you will need to locally
build install the <tt>codesign-maven-plugin</tt> from
+<a
href="https://github.com/apache/sling-whiteboard/tree/master/codesign";>https://github.com/apache/sling-whiteboard/tree/master/codesign</a>.</div>
<p>The whole process is outlined below, assuming that we start with a
development version of 1.0.1-SNAPSHOT.</p>
<ol>
<li>set the fix version as released: <code>mvn tycho-versions:set-version
-DnewVersion=1.0.2</code></li>
@@ -337,8 +342,8 @@ Enjoy!
<li>Tag the commit using <code>git tag -a -m 'Tag 1.0.2 release'
sling-ide-tooling-1.0.2</code></li>
<li>update to next version: <code>mvn tycho-versions:set-version
-DnewVersion=1.0.3-SNAPSHOT</code> and also update the version of the
source-bundle project</li>
<li>commit and push the change</li>
- <li>checkout the version from the tag and proceed with the build from there
<code>git checkout sling-ide-tooling-1.0.2</code>a</li>
- <li>In <code>p2update/pom.xml</code>, uncomment the
<code>codesign-maven-plugin</code> declaration and change the code signing
service to 'Java Signing Sha256'</li>
+ <li>checkout the version from the tag and proceed with the build from there
<code>git checkout sling-ide-tooling-1.0.2</code></li>
+ <li>In <code>p2update/pom.xml</code>, uncomment the
<code>codesign-maven-plugin</code> declaration and change the code signing
service to <em>Java Signing Sha256</em>. Note that the process might fail
during the code signing with a SAAJ error, retrying usually fixes it.</li>
<li>build the project with p2/gpg signing enabled: <code>mvn clean package
-Pcodesign</code></li>
<li>manually build the zipped p2 repository: <code>cd
p2update/target/repository-signed && zip -r
org.apache.sling.ide.p2update-1.0.2.zip . && cd -</code></li>
<li>build the source bundle from the source-bundle directory: <code>mvn
clean package</code></li>
@@ -491,7 +496,7 @@ ssb 2048R/226BCE00 2016-01-21
</ol></section></div></div>
<div class="footer">
<div class="revisionInfo">
- Last modified by <span class="author">Robert
Munteanu</span> on <span class="comment">Wed Jan 17 23:22:33 2018 +0200</span>
+ Last modified by <span class="author">Robert
Munteanu</span> on <span class="comment">Mon Feb 26 23:42:10 2018 +0200</span>
</div> <p>
Apache Sling, Sling, Apache, the Apache feather logo, and
the Apache Sling project logo are trademarks of The Apache Software Foundation.
All other marks mentioned may be trademarks or registered trademarks of their
respective owners.
</p><p>
--
To stop receiving notification emails like this one, please contact
[email protected].
