[
https://issues.apache.org/jira/browse/SLING-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829785#comment-15829785
]
Nino Martinez commented on SLING-6474:
--------------------------------------
Yes, but I think it is as trivial as upgrading to the maven-bundle-plugin
3.2.0, HOWEVER this could have severe impacts on other parts of sling, so
fixing this could have side effects.. I tried to take a quick look to see what
version of maven-bundle-plugin sling uses but where unable to find it described
in the https://github.com/apache/sling/blob/trunk/pom.xml
Where are the plugin management defined?
> Commons Metrics DOES not declare provide capability for Metrics service
> -----------------------------------------------------------------------
>
> Key: SLING-6474
> URL: https://issues.apache.org/jira/browse/SLING-6474
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Affects Versions: Commons Metrics 1.2.0
> Reporter: Nino Martinez
> Assignee: Chetan Mehrotra
> Fix For: Commons Metrics 1.2.2
>
>
> Commons Metrics needs to declare provide capability for
> org.apache.sling.commons.metrics.MetricsService in manifest.MF
> otherwise other bundles that specifies require capability on the
> MetricsService will fail to start.
> AS of maven bundle plugin 3.2.0 this will become a problem, since they fixed
> the capabilities generation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)