You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Amichai Rothman (JIRA)" <ji...@apache.org> on 2018/03/01 07:54:00 UTC

[jira] [Commented] (SLING-7522) Scheduler bundle/package version mismatch

    [ https://issues.apache.org/jira/browse/SLING-7522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381646#comment-16381646 ] 

Amichai Rothman commented on SLING-7522:
----------------------------------------

Ok, I guess it's a but in maven-bundle-plugin. Thanks!

> Scheduler bundle/package version mismatch
> -----------------------------------------
>
>                 Key: SLING-7522
>                 URL: https://issues.apache.org/jira/browse/SLING-7522
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: Commons Scheduler 2.7.2
>            Reporter: Amichai Rothman
>            Priority: Major
>
> I just tried to upgrade from scheduler 2.5.2 to 2.7.2, and it did not go smooth.
> First, there appears to be a new dependency on org.apache.sling.commons.metrics and io.dropwizard.metrics, which I didn't see documented anywhere, but ok.
> More importantly, the scheduler bundle version (and maven dependency version I specified) is 2.7.2, but the packages exported (and imported back) by the bundle is org.apache.sling.commons.scheduler;version=2.5.1. This version mismatch seems to confuse karaf, which is expecting to find 2.7.2 but doesn't, so my feature does not resolve. While there's a chance this is a bug in Karaf or there is some sort of workaround in generating the feature, the version mismatch does seem strange and a likely bug in the scheduler as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)