[
https://issues.apache.org/jira/browse/SLING-11818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17708421#comment-17708421
]
Carsten Ziegeler commented on SLING-11818:
------------------------------------------
It seems the problem is really the mock project - so if we want to fix this,
those dependencies there should be changed to be not provided.
{noformat}
[INFO] +- org.apache.sling:org.apache.sling.testing.osgi-mock:jar:2.3.2:test
[INFO] | +- org.osgi:osgi.core:jar:7.0.0:provided
[INFO] | +- org.osgi:osgi.cmpn:jar:7.0.0:provided
[INFO] | +- org.apache.commons:commons-lang3:jar:3.0.1:test
[INFO] | \- org.reflections:reflections:jar:0.9.9:test
[INFO] | +- org.javassist:javassist:jar:3.18.2-GA:test
[INFO] | \- com.google.code.findbugs:annotations:jar:2.0.1:test{noformat}
> 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)
