You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by tr...@apache.org on 2017/11/02 07:12:05 UTC

svn commit: r1814040 - /jackrabbit/commons/filevault-package-maven-plugin/trunk/src/site/markdown/migrating.md

Author: tripod
Date: Thu Nov  2 07:12:05 2017
New Revision: 1814040

URL: http://svn.apache.org/viewvc?rev=1814040&view=rev
Log:
update to released plugin version

Modified:
    jackrabbit/commons/filevault-package-maven-plugin/trunk/src/site/markdown/migrating.md

Modified: jackrabbit/commons/filevault-package-maven-plugin/trunk/src/site/markdown/migrating.md
URL: http://svn.apache.org/viewvc/jackrabbit/commons/filevault-package-maven-plugin/trunk/src/site/markdown/migrating.md?rev=1814040&r1=1814039&r2=1814040&view=diff
==============================================================================
--- jackrabbit/commons/filevault-package-maven-plugin/trunk/src/site/markdown/migrating.md (original)
+++ jackrabbit/commons/filevault-package-maven-plugin/trunk/src/site/markdown/migrating.md Thu Nov  2 07:12:05 2017
@@ -23,7 +23,7 @@ Some of the functionality of former `com
 when the code was migrated to the  `org.apache.jackrabbit:filevault-package-maven-plugin` (Jackrabbit's plugin).
 In particular, all the goals dealing with the Adobe CRX Package Manager interoperability were removed.
 
-Starting with the [1.0.0 release][0] of Adobe's plugin, all the content packaging functionality
+Starting with the [1.0.2 release][0] of Adobe's plugin, all the content packaging functionality
 was removed, so that both plugins can now be used in the same project (pom).
 
 Projects that want to migrate to Jackrabbit's plugin just need to replace the maven coordinates of the