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

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-7522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-7522.
-------------------------------------
    Resolution: Invalid

This is a tooling problem on your end. bnd and all bnd based tooling does not use the bundle version to create the import but the package version, so you are either hand crafting the import or use a tool which is buggy for this

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