- Documentation (trunk)
- Release Notes
- Classpath Container
- Non-Java dependencies
- Ivy file editor
- Ivy settings editor
- Eclipse global preferences
- Eclipse variables
- Ivy Console
- Eclipse's Ant integration
- Reverse Dependency Explorer
- Resolve Visualizer
- Developer doc
Apache IvyDE will resolve the dependencies and artifacts you are requiring. Then with the pool of resolved artifacts, it has to decide which is a binary jar, which contains sources, and which contains javadocs. And also how to bind one on each other.
Finding jars typesThere are three types of jars handled by Eclipse":
- the binary jars: they will be added to the classpath in oder to compile and run; they contain the .class files.
- the source jars/zip: they will be bound to the binary one to browse dependency sources; they are basically a zip of .java files
- the javadoc jars/zip: they will be bound to the binary one to browse the API documentation of the dependencies of your project; they are a zip of .html files respectively in a layout produced by javadoc.
For the sources, it is relying on the "Sources types".
For the javadocs, it is relying on the "Javadocs types".
Binding the jars
AlorithmThe second step is to bind a source artifact with a binary one. IvyDE has the following algorithm:
- first, it looks up for a specified name in the ivy.xml via the "ivyde" namespace (see bellow)
- next, if a binary jar has the same artifact name than a source one, there are bound together.
- if none matched, then IvyDE search for sources which have one of the suffix specified in "Sources suffixes".
The IvyDE namespaceIn the ivy.xml file in your repository, you can specifically bind a binary artifact to a source one and to a javadoc one, so IvyDE knows for sure which bind to the other.
In the artifact element, you can specify:
- ivyde:source="my-source-artifact-name" which specify the artifact name of the source to bind to the current binary one
- ivyde:javadoc="my-javadoc-artifact-name" which specify the artifact name of the javadoc to bind to the current binary one
ExemplesFor instance, searching for the sources of mylib.jar (type=jar), with the default value of "Sources suffixes" ("-source,-sources,-src"), IvyDE will look to bind it to the first one existing of:
- mylib.jar (type=source)
- mylib-source.jar (type=source)
- mylib-sources.jar (type=source)
- mylib-src.jar (type=source)
Same apply for javadocs with respectively "Javadocs suffixes".
With the IvyDE namespace, having the ivy.xml file:
<ivy-module version="2.0" xmlns:ivyde="http://ant.apache.org/ivy/ivyde/ns/">Without furether setup in IvyDE preferences pages, IvyDE will bind:
<info organisation="com.acme" module="mylib" />
<artifact name="mylib" type="jar" ext="jar" ivyde:source="the-sources-of-mylib" ivyde:javadoc="the-javadoc-of-mylib" />
<artifact name="the-sources-of-mylib" type="source" ext="jar" />
<artifact name="the-javadoc-of-mylib" type="javadoc" ext="jar" />
- the jar the-sources-of-mylib as sources of the jar mylib
- the jar the-javadoc-of-mylib as javadoc of the jar mylib