You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2023/04/04 11:53:00 UTC

[jira] [Commented] (SLING-11818) Update to Sling Parent POM 48 broke api generation

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

Konrad Windszus commented on SLING-11818:
-----------------------------------------

Dependency Management is merged with the one from the parent (from which it got the versions). It was deliberately added to always set the scope to test for those dependencies. If you remove those all dependent modules will transitively get the legacy OSGi dependency. Also I would really appreciate a PR for changes like this.

> Update to Sling Parent POM 48 broke api generation
> --------------------------------------------------
>
>                 Key: SLING-11818
>                 URL: https://issues.apache.org/jira/browse/SLING-11818
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR Base 3.1.12
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: JCR Base 3.1.14
>
>
> This commit [https://github.com/apache/sling-org-apache-sling-jcr-base/commit/97ea7f527040b1bcb0f7f9888a4c599ca91f58cb] added a buggy dependency management section to the pom without any versions. This confuses other tools like the slingfeature maven plugin.
> The whole dependency management section is not needed and can simply be removed



--
This message was sent by Atlassian Jira
(v8.20.10#820010)