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

["Amichai Rothman (JIRA)" <ji...@apache.org>]

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

Amichai Rothman edited comment on SLING-7522 at 3/1/18 12:01 AM:
-----------------------------------------------------------------

And if you also have a project bundle that depends on sling scheduler 2.7.2? Then it tries to import 2.7.2, but there's only a 2.5.1 being exported, so it fails. At least that's what happens in my scenario.

Note that I don't actually use this feature you quoted, but create an application feature that includes sling scheduler among other things (using the karaf-maven-plugin to create it), and an application bundle that consumes it (using maven-bundle-plugin). Both poms specify scheduler 2.7.2, and it doesn't work. Using previous versions (2.5.2 and earlier) this setup worked fine. I suppose I can specify 2.7.2 to be added to the feature, and 2.5.x in the consuming bundle... but that's just weird.


was (Author: amichai):
And if you also have a project bundle that depends on sling scheduler 2.7.2? Then it tries to import 2.7.2, but there's only a 2.5.1 being exported, so it fails. At least that's what happens in my scenario.

Note that I don't actually use this feature you quoted, but create an application feature that includes sling scheduler among other things (using the maven-bundle-plugin to create it), and an application bundle that consumes it. Both poms specify scheduler 2.7.2, and it doesn't work. Using previous versions (2.5.2 and earlier) this setup worked fine. I suppose I can specify 2.7.2 to be added to the feature, and 2.5.x in the consuming bundle... but that's just weird.

> 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)