From b1390a5413b264ac97539a7a4c59ecc98a38a409 Mon Sep 17 00:00:00 2001 From: Nicolas Lalevee Date: Mon, 20 Dec 2010 11:03:10 +0000 Subject: [PATCH] Add a notice about the experimental state of the OSGi capabilities of Ivy git-svn-id: https://svn.apache.org/repos/asf/ant/ivy/core/trunk@1051064 13f79535-47bb-0310-9956-ffa450edef68 --- doc/osgi.html | 6 +++++- doc/osgi/eclipse-plugin.html | 4 ++++ doc/osgi/standard-osgi.html | 4 ++++ doc/osgi/target-platform.html | 4 ++++ doc/style/style.css | 6 ++++++ 5 files changed, 23 insertions(+), 1 deletion(-) diff --git a/doc/osgi.html b/doc/osgi.html index 73cf0a1f..371cef9b 100644 --- a/doc/osgi.html +++ b/doc/osgi.html @@ -28,13 +28,17 @@ 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 discussed 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 trasitive dependencies will be resolved. You can also declare in your ivy.xml some OSGi dependency, like a Require-Bundle, an Import-Package or an Import-Service, miming an OSGi MANIFEST.MF.

Note on the implementation

With OSGi we can declare different kind of capabilites of a bundle which can match different kind of requirements of some other bundles (Require-Bundle/Bundle-SymbolicName, Import-Package/Export-Package, Import-Service/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 involing OSGi dependencies management. -Details on the mapping of the OSGi dependency model into Ivy's one can be found in that page. +Details on the mapping of the OSGi dependency model into Ivy's one can be found in that page.

Repository descriptor based resolvers

diff --git a/doc/osgi/eclipse-plugin.html b/doc/osgi/eclipse-plugin.html index 344da3d3..bfd637f1 100644 --- a/doc/osgi/eclipse-plugin.html +++ b/doc/osgi/eclipse-plugin.html @@ -26,6 +26,10 @@