You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Oliver Lietz (Jira)" <ji...@apache.org> on 2019/12/22 09:06:00 UTC
[jira] [Closed] (SLING-8672) Missing Constraint:
Require-Capability: osgi.service;
filter="(objectClass=com.codahale.metrics.MetricRegistry)"
[ https://issues.apache.org/jira/browse/SLING-8672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Lietz closed SLING-8672.
-------------------------------
> Missing Constraint: Require-Capability: osgi.service; filter="(objectClass=com.codahale.metrics.MetricRegistry)"
> ----------------------------------------------------------------------------------------------------------------
>
> Key: SLING-8672
> URL: https://issues.apache.org/jira/browse/SLING-8672
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons Scheduler 2.7.4
> Reporter: Nhut Thai Le
> Priority: Major
> Attachments: launchErr.PNG
>
>
> Hello,
> I'm using org.apache.commons.scheduler 2.7.4 and io.dropwizard.metrics.core 3.2.6. When i launch the application from eclipse, o.a.c.scheduler complains that: Missing Constraint: Require-Capability: osgi.service; filter="(objectClass=com.codahale.metrics.MetricRegistry)". The com.codahale.metrics.MetricRegistry class is defined and exported by io.dropwizard.metrics.core but dropwizard.metrics.core never declare that it provide this class as Capability (i checked a few versions of io.dropwizard.metrics.core). Is it a bug that sling.commons.scheduler requires such capability ? I havent seen this error when i was running on eclipse oxygen but with recent upgrade to eclipse 201903, this shows up.
> About our running env:
> org.eclipse.osgi 3.14.0.v20190517-1309
> org.apache.felix.scr 2.1.14.v20190123-1619
> pax-web-extender-whiteboard 7.2.10
> jetty 9.4.18.v20190429
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)