Trying to integrate a newer Version of ical4j i’m failing to get my bundle built as there is a missing dependency. The resolution of dependencies gives me a wiring error back to (&(osgi.wiring.package=net.fortuna.ical4j.data)(&(version>=3.0.0)(!(version>=4.0.0)))). From my understanding, the package net.fortuna.ical4j.data in 3.0.0 <= version < 4.0.0 is searched, which is not configured in the feature.xml:
As the current version of ical4j does not export the dependencies properly, i’d like to pin the version until this issue is fixed. Is there a way to specify the exact version?
However there are also newer versions of some dependencies available where ping may be necessary in case of trouble. I’ve also writen a small test for the logic, there (in my understanding) the dependencies defined in the pom should be used.
I assume from that behavior i should use always same versions in feature.xml and pom.xml. Is this assumption wrong?
Are you sure that one of the bundles really exports that package? I think that is the problem, because 3.0.4 is in the range mentioned above. Maybe you need to add another bundle to the feature.
In this case i wanted to pin this library as the following version had problems with the exported list. However the author Ben Fortuna has fixed it already/will fix it at next release (a Big Thank You, Mr. Fortuna!). But the library is still using specific versions of other libraries.
I have also looked up all the dependencies - but have nothing found required further. Do have another ideas how to solve?
Dependencies should now be included in a different scope. This also enables the possibility to pin a dependency. Dependencies which are likely to be used by other addons also shouldn’t be embedded - so they can be shared.