- Documentation (2.5.0-local-20170911195251)
- Release Notes
- Settings Files
- Ivy Files
- Ant Tasks
- post resolve tasks
- Using standalone
- Developer doc
Since Apache Ivy 2.3, some support for OSGi dependency management has been introduced.
|Note that this feature is considered as experimental. It should work with simple configuration but may not in complex ones. If you have any issue with that feature, you are welcomed to come discuss your use case on the ivy-user mailing list, or discuss about implementation issues or improvement you may have found, on ant-dev.|
So with a standard ivy.xml, you can express some dependency on some OSGi bundle and every of their transitive dependencies will be resolved. You can also declare in your ivy.xml some OSGi dependency, like a
Import-Package or an
Import-Service, miming an OSGi MANIFEST.MF.
Note on the implementation
With OSGi we can declare different kind of capabilities of a bundle which can match different kind of requirements of some other bundles (
Export-Service). In Ivy we only have one kind of requirement and one kind of capability: the symbolic name of the bundle. Due to that restriction Ivy may not resolve exactly how we would expect with OSGi. The runtime of Ivy won’t be as smart as a pure OSGi dependency manager. But we think that the mapping is working for most of the use cases involving OSGi dependencies management.
Details on the mapping of the OSGi dependency model into Ivy’s one can be found in this page.
Repository descriptor based resolvers
Since the nature of the OSGi dependencies, resolving against a repository cannot be started before acquiring the metadata of every bundle of the repository. To resolve an
Import-Package, Ivy has to find every bundle which has the proper
Export-Package. So unlike the usual Ivy resolvers, the OSGi capable ones have to get the descriptor before starting a resolve.
The descriptor probably being not instantly downloaded, the descriptor is put in cache. (FIXME not implemented)