You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sis.apache.org by de...@apache.org on 2018/11/04 20:32:02 UTC
svn commit: r1845746 - in /sis/site/trunk/content: build.mdtext
release-management.mdtext
Author: desruisseaux
Date: Sun Nov 4 20:32:02 2018
New Revision: 1845746
URL: http://svn.apache.org/viewvc?rev=1845746&view=rev
Log:
Remove references to PACK200 since this format has been deprecated for removal in Java 11.
This commit is part of https://issues.apache.org/jira/browse/SIS-430.
Modified:
sis/site/trunk/content/build.mdtext
sis/site/trunk/content/release-management.mdtext
Modified: sis/site/trunk/content/build.mdtext
URL: http://svn.apache.org/viewvc/sis/site/trunk/content/build.mdtext?rev=1845746&r1=1845745&r2=1845746&view=diff
==============================================================================
--- sis/site/trunk/content/build.mdtext [UTF-8] (original)
+++ sis/site/trunk/content/build.mdtext [UTF-8] Sun Nov 4 20:32:02 2018
@@ -38,10 +38,10 @@ The remaining of this page provides more
-Distribution file and Pack200 bundle {#dist}
-==============================================
+Distribution file {#dist}
+===========================
-The Pack200 bundle is a file with the `.pack.gz` extension containing most SIS modules except `sis-webapp`
+The distribution archive is a file with the `.zip` extension containing most SIS modules except `sis-webapp`
(because Web applications use an other packaging) together with their dependencies.
Pack200 files are uncompressed by the `unpack200` command provided in JDK/JRE installation.
However for users convenience, we provide a shell script for uncompressing and launching the SIS
@@ -62,25 +62,6 @@ To test, uncompress in any directory and
The Pack200 file will be automatically uncompressed when first needed.
-Generating the Pack200 file alone {#pack200}
-----------------------------------------------
-
-If only the Pack200 file is desired, without the distribution ZIP file, one can use the following command
-(do not forget the `--non-recursive` option, otherwise the Mojo will waste CPU by executing itself many time):
-
- :::bash
- mvn org.apache.sis.core:sis-build-helper:pack --non-recursive
-
-The above command should create a `target/distribution/apache-sis-<version>.pack.gz` file.
-To uncompress that file, use the following command:
-
- :::bash
- unpack200 --remove-pack-file apache-sis-<version>.pack.gz sis.jar
-
-The Pack200 bundle does not include the `sis-webapp` module because the later can be downloaded
-as a `WAR` file from the Maven repository.
-
-
Known limitations {#limitations}
----------------------------------
@@ -88,7 +69,6 @@ Known limitations {#limitations}
The current plugin implementation has some hard-coded values, especially:
* The ZIP file content is copied from the `application/sis-console/src/main/artifact` directory.
- * The Pack200 file path inside the ZIP file is hard-coded to `lib/sis.pack.gz`.
* The final filename is hard-coded to `apache-sis-<version>.zip`.
Modified: sis/site/trunk/content/release-management.mdtext
URL: http://svn.apache.org/viewvc/sis/site/trunk/content/release-management.mdtext?rev=1845746&r1=1845745&r2=1845746&view=diff
==============================================================================
--- sis/site/trunk/content/release-management.mdtext [UTF-8] (original)
+++ sis/site/trunk/content/release-management.mdtext [UTF-8] Sun Nov 4 20:32:02 2018
@@ -165,9 +165,9 @@ This profile performs the following acti
* Enable extensive tests (i.e. it will set the `org.apache.sis.test.extensive` property to `true`).
* Generate Javadoc. This may fail if the source code contains invalid Javadoc tags or broken HTML.
- * Generate additional binary artifacts (`*.pack.gz` and `*.oxt` files).
+ * Generate additional binary artifacts (`*.zip` and `*.oxt` files).
This will fail if duplicated class files or resources are found.
- Consequently building the `.*pack.gz` file is an additional test worth to do before deployment.
+ Consequently building the `*.zip` file is an additional test worth to do before deployment.
* Sign the artifacts.
Each of those additional products may cause a failure that did not happen in normal builds.