karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Lietz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-201) Add post feature installation triggers
Date Mon, 06 Feb 2017 13:28:41 GMT

    [ https://issues.apache.org/jira/browse/KARAF-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15853985#comment-15853985

Oliver Lietz commented on KARAF-201:

Sorry, no. Database migration was an example and it could be any task. In my case it is a
[Java Content Repository (JCR)|http://jackrabbit.apache.org/jcr/jcr-api.html], concretely
[Apache Jackrabbit Oak|https://jackrabbit.apache.org/oak/] (Oak runs with Tar, Mongo or RDBMS
_backend_). _On top_ of Oak sits [Sling|https://sling.apache.org] and provides services to
access resources (from Oak but not only). Now you install applications _on top_ of Sling and
in some cases you need to transform, add, remove or move existing content before these applications
are installed (updated) – this is a concrete example close to database migration but I can
imagine more use cases.

> Add post feature installation triggers
> --------------------------------------
>                 Key: KARAF-201
>                 URL: https://issues.apache.org/jira/browse/KARAF-201
>             Project: Karaf
>          Issue Type: New Feature
>          Components: karaf-core, karaf-feature
>            Reporter: Guillaume Nodet
>             Fix For: 4.1.1
> Something like:
> {code}
> <script trigger="post">
>     // do anything using gogo commands
> </script>
> {code}
> The result could be displayed to the user so that the installation could give him some
information (manual steps, or whatever), though it may need a separate element.

This message was sent by Atlassian JIRA

View raw message