Create FileVault Packages with Content Package Maven Plugin

Description

----Original Message----
From: wcm-io-dev@googlegroups.com wcm-io-dev@googlegroups.com On Behalf Of Andreas Schaefer
Sent: Wednesday, May 10, 2017 8:25 PM
To: wcm-io-dev@googlegroups.com
Cc: Andreas Schaefer
Subject: Re: Content Package Maven Plugin

Hi Stefan

I create a PR for the JCR Content Packager:

https://github.com/wcm-io/wcm-io-tooling/pull/14

While testing it I discovered that looping of the Filter is not going to work without
major adjustments and so I ditched that for now.

The rest is more or less the same as the Adobe’s 'content-package-maven-plugin’
except the ‘generateFilter’ and ‘acHandling’ Mojo property. Both were confusing
me for the longest time and so I changed them here.

The packager requires that all content is placed in the work-directory (target/vault-work/jcr_root)
otherwise it will be ignored.

I tested it with a simple wrapper package (to install the project packages and bundles)
in one swoop and with a content / nested packages and embedded bundles.

This is the POM for Slingbucks2:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 <packaging>content-package</packaging> .. <plugin> <groupId>io.wcm.maven.plugins</groupId> <artifactId>wcmio-content-package-maven-plugin</artifactId> <version>1.4.3-SNAPSHOT</version> <extensions>true</extensions> <executions> <execution> <goals> <goal>package</goal> </goals> <configuration> <group>org.apache.sling</group> <!-- Merge the Permissions --> <acHandling>MERGE</acHandling> <embeddedTarget>/apps/slingbucks2App/install</embeddedTarget> <embeddeds> <embedded> <groupId>${project.groupId}</groupId> <artifactId>core.slingbucks</artifactId> <generateFilter>true</generateFilter> </embedded> </embeddeds> <subPackages> <subPackage> <groupId>${project.groupId}</groupId> <artifactId>ui.apps.user</artifactId> <generateFilter>true</generateFilter> </subPackage> </subPackages> <!-- ATTENTION: Do not include this package as sub package which would yield an endless loop --> </configuration> </execution> </executions> </plugin>

Let me know if that works for you.

  • Andy

Environment

None

Status

Assignee

Unassigned

Reporter

Stefan Seifert

Labels

None

Components

Fix versions

Priority

Major
Configure