[
https://issues.apache.org/jira/browse/SLING-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647927#comment-15647927
]
Robert Munteanu edited comment on SLING-6256 at 11/8/16 3:54 PM:
-----------------------------------------------------------------
Since this would effectively restrict where the IDE tooling runs I would prefer
to keep the requirements low. Can we perhaps override the OSGi deps to keep
them at the same level? If you need a more precise answer you'd need to wait
while I check the minimum dependencies for older AEM versions :-)
was (Author: rombert):
Since this would effectively restrict where the IDE tooling runs I would prefer
to keep the requirements low. Can we perhaps override the OSGi deps to keep
them at the same level? If you need a more precise answer you'd need to wait
while I check the minimum dependencies for older AEM versions.
> Tooling Support: Fragments are listed twice as source reference
> ---------------------------------------------------------------
>
> Key: SLING-6256
> URL: https://issues.apache.org/jira/browse/SLING-6256
> Project: Sling
> Issue Type: Bug
> Components: Tooling
> Affects Versions: Tooling Support Source 1.0.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Fix For: Tooling Support Source 1.0.2
>
>
> All bundle fragments appear twice in the JSON output of
> {{/system/sling/tooling/sourceReferences.json}} because once they are listed
> with their host bundle and once on their own. I think it makes sense to only
> consider real bundles (with all their bound fragments) and skip the
> individual fragments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
