Managing a target platform | Apache Ivy™ 2.3.0 Documentation

# Managing a target platform
| 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.
TODO - WORK IN PROGRESS Building an OSGi™ bundle with standard tools like `javac` and a classpath computed by Apache Ivy™ can be erroneous as these tools doesn't take into account the package visibility enforced by the OSGi metadata. Then switching to OSGi dedicated tools like the Eclipse™ JDT can be prefered. This kind of tools still need a "target platform", a set of jars against to compile and then later run. A target platform can be easily managed with Ivy and its OSGi capabilities. Some links of interest: OSGi Bundle Repository Resolver Eclipse updatesite Resolver Ant ivy:retrieve task