sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seifert (JIRA)" <>
Subject [jira] [Commented] (SLING-7277) Sling Maven Archetype for a Wrapper Content Package with a Content and Bundle
Date Thu, 07 Dec 2017 16:23:00 GMT


Stefan Seifert commented on SLING-7277:

why creating a separate archetype for two quite similar variants with and without "all" package?
(this ticket and SLING-7276) - i assume there is a lot of redundancy which makes maintenance
hard. your can easily combine them and make the "all" package optional via an additional archetype
parameter. this feature of maven archetype is not very well documented, but it's possible
with a but of custom groovy script - a (rather complex) example:

i tried you archetypes but i was not able to use it after compiling it local - it was not
found by the archetype:generate goal. perhaps the issue is that the archetype plugin version
you reference indirectly from the parent pom is very outdated (~6 years)? i have not looked
deepter into this.

normally the integration tests are executed automatically by the archetype plugin if the archetype
itself is built locally - you describe a script "sh" should be
used, but this does not exist.

one remark on the wcmio-content-package-maven-plugin: since some months the jackrabbit project
published their own open source version of the package plugin (only supporting building packages,
not the up/downloading from crx package manager or composum). we should use this instead of
the content package plugin. i've published a migration guide

> Sling Maven Archetype for a Wrapper Content Package with a Content and Bundle
> -----------------------------------------------------------------------------
>                 Key: SLING-7277
>                 URL:
>             Project: Sling
>          Issue Type: New Feature
>          Components: Tooling
>         Environment: Sling 9
>            Reporter: Andreas Schaefer
>              Labels: Archetype, Maven
> This Maven Archetype creates a wrapper Content Package (all) that contains an OSGi Bundle
(core) and a Content Package (ui.apps).
> This does the same thing if there is only one content package but for bigger projects
containing multiple content packages and bundles this can make sure that everything is deployed
as an atomic file preventing issues with dependencies and out of sync content.
> The Git Repository for this is here:

This message was sent by Atlassian JIRA

View raw message