[
https://issues.apache.org/jira/browse/SLING-11818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17708391#comment-17708391
]
Carsten Ziegeler edited comment on SLING-11818 at 4/4/23 11:55 AM:
-------------------------------------------------------------------
[~kwin] First of all these dependencies are not used in the pom at all; second
as I wrote it broke tooling - and it is ironic that you ask for a PR where your
change which broke it was done without a PR
was (Author: cziegeler):
[~kwin] First of all these dependencies are not used in the pom at all; second
as I wrote it broke tooling
> 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)
