You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Karl Pauls (Jira)" <ji...@apache.org> on 2021/05/21 09:58:00 UTC

[jira] [Commented] (SLING-10401) Ease usage of cp2fm as library

    [ https://issues.apache.org/jira/browse/SLING-10401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349122#comment-17349122 ] 

Karl Pauls commented on SLING-10401:
------------------------------------

I moved the issue to the next release as I want to quickly do a 1.1.2 that contains only the bug fixes we have for 1.1.0.

> Ease usage of cp2fm as library
> ------------------------------
>
>                 Key: SLING-10401
>                 URL: https://issues.apache.org/jira/browse/SLING-10401
>             Project: Sling
>          Issue Type: Improvement
>          Components: Content-Package to Feature Model Converter
>            Reporter: Konrad Windszus
>            Priority: Major
>             Fix For: Content-Package to Feature Model Converter 1.1.4
>
>
> Currently all dependencies are marked as {{provided}} although cp2fm is never executed in some sort of container but either used standalone or used as library e.g. from Maven plugins. For the latter a scope of {{compile}} is much better, as that way dependencies are transitive. Otherwise every consumer has to redefine all used dependencies (very error prone). Compare with https://github.com/adobe/aemanalyser-maven-plugin/issues/58.



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