You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "A. J. David Bosschaert (Jira)" <ji...@apache.org> on 2020/05/13 16:04:00 UTC

[jira] [Resolved] (SLING-9443) Access Feature Model Aggregates as Files during Maven Build

     [ https://issues.apache.org/jira/browse/SLING-9443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

A. J. David Bosschaert resolved SLING-9443.
-------------------------------------------
    Resolution: Fixed

Merged https://github.com/apache/sling-slingfeature-maven-plugin/pull/52

> Access Feature Model Aggregates as Files during Maven Build
> -----------------------------------------------------------
>
>                 Key: SLING-9443
>                 URL: https://issues.apache.org/jira/browse/SLING-9443
>             Project: Sling
>          Issue Type: Improvement
>          Components: Feature Model
>    Affects Versions: slingfeature-maven-plugin 1.3.0
>            Reporter: A. J. David Bosschaert
>            Assignee: A. J. David Bosschaert
>            Priority: Major
>             Fix For: slingfeature-maven-plugin 1.3.2
>
>
> When the Feature Aggregates are generated, they are initially kept in memory. The slingfeature-maven-plugin can access them there, but they cannot be accessed by other plugins as they won't share the same classloaders.
> For other plugins to use these aggregates we need to have them available on the filesystem. Therefore the feature should be written to the file system as soon as the aggregate is created.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)