You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by kw...@apache.org on 2022/07/01 11:52:06 UTC
[jackrabbit-filevault-package-maven-plugin] branch master updated: fix some links, clarify usage of extensions
This is an automated email from the ASF dual-hosted git repository.
kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/jackrabbit-filevault-package-maven-plugin.git
The following commit(s) were added to refs/heads/master by this push:
new a78e114 fix some links, clarify usage of extensions
a78e114 is described below
commit a78e114b8b7cb14126a5f244721cc23de7ba7426
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Fri Jul 1 13:52:01 2022 +0200
fix some links, clarify usage of extensions
---
src/site/markdown/migrating.md | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/src/site/markdown/migrating.md b/src/site/markdown/migrating.md
index 9063410..131c28e 100644
--- a/src/site/markdown/migrating.md
+++ b/src/site/markdown/migrating.md
@@ -27,9 +27,11 @@ In particular, all the goals dealing with the Adobe's CRX Package Manager intero
Starting with the [1.0.2 release][0] of Adobe's plugin, all the content package build 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 <aven coordinates of the
+Projects that want to migrate to Jackrabbit's plugin just need to replace the Maven coordinates of the
content package plugin. And, if the package manager goals are still needed, add Adobe's plugin again.
+The Adobe plugin since 1.0.2 does no longer come with any extensions or custom lifecycle mapping, so you can remove `<extensions>true</extension>` on it.
+
Example
-------
An example plugin section could look like this:
@@ -40,6 +42,7 @@ An example plugin section could look like this:
<groupId>org.apache.jackrabbit</groupId>
<artifactId>filevault-package-maven-plugin</artifactId>
<version>1.0.0</version>
+ <extensions>true</extensions>
<configuration>
<filterSource>${basedir}/META-INF/vault/filter.xml</filterSource>
</configuration>
@@ -58,10 +61,11 @@ Next Steps
Currently there is no roadmap for implementing a package manager in Jackrabbit. Some ideas are tracked in [JCRVLT-151][1],
but until then, the plugin will not support any deployment options.
-
-Alternatively, projects can use the 3rd party [Composum Package Manager][2] together with Adobe's plugin.
+
+Alternatively, projects can use the 3rd party [Composum Package Manager][2] together with Adobe's plugin or the [wcm.io Content Package Maven Plugin][3].
[0]: https://repo1.maven.org/maven2/com/day/jcr/vault/content-package-maven-plugin/
[1]: https://issues.apache.org/jira/browse/JCRVLT-151
-[2]: https://ist-software.atlassian.net/wiki/spaces/CMP/pages/46140125/Package+Manager
+[2]: https://www.composum.com/home/nodes/pckgmgr.html
+[3]: https://wcm.io/tooling/maven/plugins/wcmio-content-package-maven-plugin/
\ No newline at end of file