sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1036734 - in /websites/staging/sis/trunk/content: ./ build.html release-management.html
Date Sun, 04 Nov 2018 20:32:13 GMT
Author: buildbot
Date: Sun Nov  4 20:32:13 2018
New Revision: 1036734

Staging update by buildbot for sis

    websites/staging/sis/trunk/content/   (props changed)

Propchange: websites/staging/sis/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Sun Nov  4 20:32:13 2018
@@ -1 +1 @@

Modified: websites/staging/sis/trunk/content/build.html
--- websites/staging/sis/trunk/content/build.html (original)
+++ websites/staging/sis/trunk/content/build.html Sun Nov  4 20:32:13 2018
@@ -116,8 +116,7 @@ Note that it requires an OpenPGP (<em>Op
 <p>The remaining of this page provides more advanced tips for SIS developers.</p>
 <div class="toc">
-<li><a href="#dist">Distribution file and Pack200 bundle</a><ul>
-<li><a href="#pack200">Generating the Pack200 file alone</a></li>
+<li><a href="#dist">Distribution file</a><ul>
 <li><a href="#limitations">Known limitations</a></li>
@@ -128,8 +127,8 @@ Note that it requires an OpenPGP (<em>Op
-<h1 id="dist">Distribution file and Pack200 bundle<a class="headerlink" href="#dist"
title="Permanent link">&para;</a></h1>
-<p>The Pack200 bundle is a file with the <code>.pack.gz</code> extension
containing most SIS modules except <code>sis-webapp</code>
+<h1 id="dist">Distribution file<a class="headerlink" href="#dist" title="Permanent
+<p>The distribution archive is a file with the <code>.zip</code> extension
containing most SIS modules except <code>sis-webapp</code>
 (because Web applications use an other packaging) together with their dependencies.
 Pack200 files are uncompressed by the <code>unpack200</code> command provided
in JDK/JRE installation.
 However for users convenience, we provide a shell script for uncompressing and launching
the SIS
@@ -147,26 +146,10 @@ if there is many versions of the plugin
 <p>The result will be created in the <code>target/distribution/apache-sis-&lt;version&gt;.zip</code>
 To test, uncompress in any directory and execute <code>apache-sis-&lt;version&gt;/bin/sis</code>.
 The Pack200 file will be automatically uncompressed when first needed.</p>
-<h2 id="pack200">Generating the Pack200 file alone<a class="headerlink" href="#pack200"
title="Permanent link">&para;</a></h2>
-<p>If only the Pack200 file is desired, without the distribution ZIP file, one can
use the following command
-(do not forget the <code>--non-recursive</code> option, otherwise the Mojo will
waste CPU by executing itself many time):</p>
-<div class="codehilite"><pre>mvn org.apache.sis.core:sis-build-helper:pack --non-recursive
-<p>The above command should create a <code>target/distribution/apache-sis-&lt;version&gt;.pack.gz</code>
-To uncompress that file, use the following command:</p>
-<div class="codehilite"><pre>unpack200 --remove-pack-file apache-sis-&lt;version&gt;.pack.gz
-<p>The Pack200 bundle does not include the <code>sis-webapp</code> module
because the later can be downloaded
-as a <code>WAR</code> file from the Maven repository.</p>
 <h2 id="limitations">Known limitations<a class="headerlink" href="#limitations"
title="Permanent link">&para;</a></h2>
 <p>The current plugin implementation has some hard-coded values, especially:</p>
 <li>The ZIP file content is copied from the <code>application/sis-console/src/main/artifact</code>
-<li>The Pack200 file path inside the ZIP file is hard-coded to <code>lib/sis.pack.gz</code>.</li>
 <li>The final filename is hard-coded to <code>apache-sis-&lt;version&gt;.zip</code>.</li>
 <h1 id="build-helper">SIS-specific Maven plugin<a class="headerlink" href="#build-helper"
title="Permanent link">&para;</a></h1>

Modified: websites/staging/sis/trunk/content/release-management.html
--- websites/staging/sis/trunk/content/release-management.html (original)
+++ websites/staging/sis/trunk/content/release-management.html Sun Nov  4 20:32:13 2018
@@ -258,9 +258,9 @@ This profile performs the following acti
 <li>Enable extensive tests (i.e. it will set the <code>org.apache.sis.test.extensive</code>
property to <code>true</code>).</li>
 <li>Generate Javadoc. This may fail if the source code contains invalid Javadoc tags
or broken HTML.</li>
-<li>Generate additional binary artifacts (<code>*.pack.gz</code> and <code>*.oxt</code>
+<li>Generate additional binary artifacts (<code>*.zip</code> and <code>*.oxt</code>
     This will fail if duplicated class files or resources are found.
-    Consequently building the <code>.*pack.gz</code> file is an additional test
worth to do before deployment.</li>
+    Consequently building the <code>*.zip</code> file is an additional test worth
to do before deployment.</li>
 <li>Sign the artifacts.</li>
 <p>Each of those additional products may cause a failure that did not happen in normal

View raw message