jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tri...@apache.org
Subject svn commit: r1814810 - in /jackrabbit/commons/filevault/trunk: RELEASE-NOTES.txt pom.xml vault-doc/src/site/markdown/howto_release.md
Date Fri, 10 Nov 2017 02:30:08 GMT
Author: tripod
Date: Fri Nov 10 02:30:08 2017
New Revision: 1814810

URL: http://svn.apache.org/viewvc?rev=1814810&view=rev
Log:
Prepare 3.1.42 release

Modified:
    jackrabbit/commons/filevault/trunk/RELEASE-NOTES.txt
    jackrabbit/commons/filevault/trunk/pom.xml
    jackrabbit/commons/filevault/trunk/vault-doc/src/site/markdown/howto_release.md

Modified: jackrabbit/commons/filevault/trunk/RELEASE-NOTES.txt
URL: http://svn.apache.org/viewvc/jackrabbit/commons/filevault/trunk/RELEASE-NOTES.txt?rev=1814810&r1=1814809&r2=1814810&view=diff
==============================================================================
--- jackrabbit/commons/filevault/trunk/RELEASE-NOTES.txt (original)
+++ jackrabbit/commons/filevault/trunk/RELEASE-NOTES.txt Fri Nov 10 02:30:08 2017
@@ -1,4 +1,4 @@
-Release Notes -- Apache Jackrabbit FileVault -- Version 3.1.40
+Release Notes -- Apache Jackrabbit FileVault -- Version 3.1.42
 
 Introduction
 ------------
@@ -9,6 +9,36 @@ create portable packages of repository c
 The Vault Command Line Interface aka _vlt_ that provides a subversion like
 utility to work and develop with repository content.
 
+
+Changes in Jackrabbit FileVault 3.1.42
+--------------------------------------
+
+Release Notes - Jackrabbit FileVault - Version 3.1.42
+
+Bug Fixes:
+* [JCRVLT-185] - JcrPackageManagerImpl#extract() javadoc mentions not existent "register"
property
+* [JCRVLT-186] - rcp fails to copy binaries correctly
+* [JCRVLT-197] - AggregateImpl.includesProperty fails with multiple filter roots
+* [JCRVLT-198] - Creating a package with specific path fails to import
+* [JCRVLT-225] - vlt doesn't work anymore with latest jackrabbit
+* [JCRVLT-226] - vlt doesn't work with java 9
+* [JCRVLT-227] - Import fails if user does not have access to the root path
+
+Improvements:
+* [JCRVLT-170] - Introduce the concept of package types
+* [JCRVLT-171] - Introduce the concept of Package Registry
+* [JCRVLT-172] - Introduce Package Persistence Layer
+* [JCRVLT-188] - Ensure that hollow packages still provide PackageProperties and JcrPackageDefinition.
+* [JCRVLT-190] - Provide mechanism to install several packages at once
+* [JCRVLT-191] - Make VaultPackage and JcrPackage AutoCloseable
+* [JCRVLT-192] - Deprecated exact storage location (/etc/packages)
+* [JCRVLT-196] - Add remapping support for other than renames
+* [JCRVLT-220] - Include package type when assembling a package
+
+Wont't Fix:
+* [JCRVLT-200] - Vault should support suppressSnapshots property
+
+
 Changes in Jackrabbit FileVault 3.1.40
 --------------------------------------
 

Modified: jackrabbit/commons/filevault/trunk/pom.xml
URL: http://svn.apache.org/viewvc/jackrabbit/commons/filevault/trunk/pom.xml?rev=1814810&r1=1814809&r2=1814810&view=diff
==============================================================================
--- jackrabbit/commons/filevault/trunk/pom.xml (original)
+++ jackrabbit/commons/filevault/trunk/pom.xml Fri Nov 10 02:30:08 2017
@@ -173,7 +173,12 @@
                                                 <include name="*.zip" />
                                             </fileset>
                                         </checksum>
-                                        <checksum algorithm="SHA1" fileext=".sha">
+                                        <checksum algorithm="SHA1" fileext=".sha1">
+                                            <fileset dir="${basedir}/target/${project.version}">
+                                                <include name="*.zip" />
+                                            </fileset>
+                                        </checksum>
+                                        <checksum algorithm="SHA-512" fileext=".sha512">
                                             <fileset dir="${basedir}/target/${project.version}">
                                                 <include name="*.zip" />
                                             </fileset>
@@ -194,6 +199,9 @@ https://svn.apache.org/repos/asf/jackrab
 
 The SHA1 checksum of the archive is ${checksum}.
 
+The command for running automated checks against this release candidate is:
+$ sh check-release.sh filevault ${project.version} ${checksum}
+
 A staged Maven repository is available for review at:
 
 https://repository.apache.org/

Modified: jackrabbit/commons/filevault/trunk/vault-doc/src/site/markdown/howto_release.md
URL: http://svn.apache.org/viewvc/jackrabbit/commons/filevault/trunk/vault-doc/src/site/markdown/howto_release.md?rev=1814810&r1=1814809&r2=1814810&view=diff
==============================================================================
--- jackrabbit/commons/filevault/trunk/vault-doc/src/site/markdown/howto_release.md (original)
+++ jackrabbit/commons/filevault/trunk/vault-doc/src/site/markdown/howto_release.md Fri Nov
10 02:30:08 2017
@@ -44,9 +44,11 @@ Release management tasks
     details. Make sure you have added the pgp key information in you maven settings file,
especially if you have 
     more than one key installed locally. See [Appendix B](#B) for the details.
     
-    0. (optional, prepare your environment. e.g.: `$ export version=3.1.36`)
-    1. Execute `mvn release:prepare`. This will update the POM files and tag the release
in svn (btw: specifying the release version on the commandline doesn't update the module poms
anymore lately).
-    2. Execute `mvn release:perform -Papache-release`. This will build the tagged release
and deploy the artifacts to
+    1. (optional, prepare your environment. e.g.: `$ export version=3.1.36`)
+    2. Execute `mvn clean deploy -Papache-release -Dmaven.deploy.skip=true`. This tests if
the release would work.
+    3. Execute `mvn release:prepare`. This will update the POM files and tag the release
in svn (btw: specifying the
+        release version on the commandline doesn't update the module poms anymore lately).
+    4. Execute `mvn release:perform -Papache-release`. This will build the tagged release
and deploy the artifacts to
         a new staging repository on _repository.apache.org_. 
         After the build, login to [https://repository.apache.org/][2] and you should see
it there.
     



Mime
View raw message