You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by hi...@apache.org on 2010/12/07 01:00:30 UTC
svn commit: r1042869 [12/15] - in /ant/ivy/site/target/ivyde/history: 1.2.0/
1.2.0/style/ 2.0.0.alpha1/ 2.0.0.alpha1/style/ 2.0.0.beta1/
2.0.0.beta1/dev/ 2.0.0.beta1/style/ 2.0.0.final/ 2.0.0.final/cpc/
2.0.0.final/dev/ 2.0.0.final/style/ 2.1.0/ 2.1.0/...
Modified: ant/ivy/site/target/ivyde/history/trunk/book.html
URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/trunk/book.html?rev=1042869&r1=1042868&r2=1042869&view=diff
==============================================================================
--- ant/ivy/site/target/ivyde/history/trunk/book.html (original)
+++ ant/ivy/site/target/ivyde/history/trunk/book.html Tue Dec 7 00:00:26 2010
@@ -23,7 +23,7 @@
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<title>Documentation (trunk) | IvyDE</title>
+<title>Documentation (trunk) | Apache IvyDE™</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" type="text/css" href="style/print-style.css" />
@@ -37,16 +37,16 @@
cellpadding="0" cellspacing="0" width="100%">
<tr>
<td id="home" width="30%"><a href="http://ant.apache.org/"
- title="Apache Ant"><img src="images/ant-group-logo.gif" alt="Apache Ant"
+ title="Apache Ant™"><img src="images/ant-group-logo.gif" alt="Apache Ant™"
border="0" /></a></td>
<td class="product" width="70%" align="right" valign="middle"><img
- src="images/logo.png" alt="ivy" border="0" /></td>
+ src="images/logo.png" alt="Apache IvyDE™" border="0" /></td>
</tr>
</table>
<div id="main">
- <div id="xooki-messages" onclick="xooki.html.hide('xooki-messages')" style="zIndex:999;display:none;position:absolute;top:30px;padding:10px;border-style:solid;background:#eeeeee;"></div><div class='toc-title toc-title-1'>Documentation (trunk)</div><br class="xooki-br"/>IvyDE is the Eclipse plugin which integrates Ivy into your java development enviromnent. A summary of the features it provides follows:
+ <div id="xooki-messages" onclick="xooki.html.hide('xooki-messages')" style="zIndex:999;display:none;position:absolute;top:30px;padding:10px;border-style:solid;background:#eeeeee;"></div><div class='toc-title toc-title-1'>Documentation (trunk)</div><br class="xooki-br"/>Apache IvyDE is the Eclipse plugin which integrates Apache Ivy's dependency management into Eclipse™. It lets you manage your dependencies declared in an ivy.xml in your Java Eclipse projects, or any other kind of project which needs dependency management.<br class="xooki-br"/><br class="xooki-br"/>A summary of the features it provides follows:
<ul>
<li><a href="cp_container.html">Managed classpath container</a>: automatic downloads, access to the Ivy "resolve" task from your IDE, and a <a href="cpc/workspace.html">feature</a> allowing you to develop interdependent multi-module applications in one workspace.</li>
<li><a href="ivyeditor.html">Ivy XML files editor</a>: creation wizard, html preview and completion for Ivy XML tags, attributes, and attribute values.</li>
@@ -55,21 +55,82 @@
<li><a href="revdepexplorer.html">Reverse Dependency Explorer</a>: helps you work with conflicting dependencies amongst several projects.</li>
</ul>
-IvyDE can be also used with other plugins like <a href="cpc/wtp.html">WTP</a> and <a href="ant.html">Ant</a>.<br class="xooki-br"/><br class="xooki-br"/><hr/><div class='toc-title toc-title-2'>Compatibility</div><br class="xooki-br"/><h2>Upgrading/Downgrading</h2>
+Apache IvyDE can be also used with other plugins like <a href="cpc/wtp.html">WTP</a> and <a href="ant.html">Apache Ant</a>.<br class="xooki-br"/><br class="xooki-br"/><hr/><div class='toc-title toc-title-2'>Release Notes</div><br class="xooki-br"/><ol>
+ <li><a href="#annoucement">Release Annoucement</a></li>
+ <li><a href="#what">What is Apache IvyDE?</a></li>
+ <li><a href="#status">Status of this release</a></li>
+ <li><a href="#majorchanges">Major Changes in this Release</a></li>
+ <li><a href="#contrib">Committers and Contributors for this Release</a></li>
+ <li><a href="#changes">List of Changes in this Release</a></li>
+</ol>
+
+<h1><a name="annoucement"></a>Release Annoucement</h1>
+
+<tt>
+The Apache IvyDE project is pleased to announce its 2.2.0 beta release.<br class="xooki-br"/><br class="xooki-br"/>Apache IvyDE is the Eclipse plugin which integrates Apache Ivy's dependency management into Eclipse. It lets you manage your dependencies declared in an ivy.xml in your Java Eclipse projects, or any other kind of project which needs dependency management. Apache IvyDE will contribute to the classpath of your Java project or you can make it retrieve your dependencies directly into your project. Last but not least Apache IvyDE offer editors of ivy.xml and ivysettings.xml files with completion. Get some preview here: <a href="http://ant.apache.org/ivy/ivyde/screenshots.html">http://ant.apache.org/ivy/ivyde/screenshots.html</a><br class="xooki-br"/><br class="xooki-br"/>Major changes in this release:<br class="xooki-br"/>* a synchronous resolve job has been introduced to take into account projet's inter dependencies and avoid too many workspace build,<br class="xook
i-br"/>* resolved classpath can now be based on retrieved artifacts,<br class="xooki-br"/>* IvyDE retrieve feature can now be use on non Java projets<br class="xooki-br"/><br class="xooki-br"/>Compatibility:<br class="xooki-br"/>* this release is expected to work with every version of Ivy 2.1 or superior<br class="xooki-br"/>* as for this release and the next ones, IvyDE now expects to be installed in Eclipse 3.4 or superior.<br class="xooki-br"/><br class="xooki-br"/>This release is considered as beta since the important changes in IvyDE resolve feature. We encourage our early users to test it and report us any issue they found.<br class="xooki-br"/><br class="xooki-br"/>A more detailed release notes can be read there:<br class="xooki-br"/><a href="http://ant.apache.org/ivy/ivyde/history/latest-milestone/release-notes.html">http://ant.apache.org/ivy/ivyde/history/latest-milestone/release-notes.html</a><br class="xooki-br"/><br class="xooki-br"/>Issues should be reported to:
<br class="xooki-br"/><a href="https://issues.apache.org/jira/browse/IVYDE">https://issues.apache.org/jira/browse/IVYDE</a><br class="xooki-br"/><br class="xooki-br"/>Download the 2.2.0 beta release at:<br class="xooki-br"/><a href="http://ant.apache.org/ivy/ivyde/download.cgi">http://ant.apache.org/ivy/ivyde/download.cgi</a><br class="xooki-br"/><br class="xooki-br"/>Or use directly the Apache IvyDE's updatesite:<br class="xooki-br"/><a href="http://www.apache.org/dist/ant/ivyde/updatesite">http://www.apache.org/dist/ant/ivyde/updatesite</a><br class="xooki-br"/><br class="xooki-br"/>More information can be found on the Apache IvyDE website:<br class="xooki-br"/><a href="http://ant.apache.org/ivy/ivyde/">http://ant.apache.org/ivy/ivyde/</a><br class="xooki-br"/></tt>
-This version is compatible with every earlier Apache release (since 2.0.0.alpha1). Any upgrade of IvyDE should work without any worries.<br class="xooki-br"/><br class="xooki-br"/>The reverse is not true, downgrading is not supported and may break your configuration<br class="xooki-br"/><br class="xooki-br"/><h2>Dependency on Ivy</h2>
+<h1><a name="what"></a>What is Apache IvyDE?</h1>
-IvyDE expects to be used with a version 2.1 or superior of Ivy.<br class="xooki-br"/><br class="xooki-br"/><h2>Eclipse integration</h2>
+Apache IvyDE is the Eclipse plugin which integrates Apache Ivy's dependency management into Eclipse™.<br class="xooki-br"/><br class="xooki-br"/>Apache IvyDE lets you manage your dependencies declared in an ivy.xml in your Java Eclipse projects, or any other kind of project which needs dependency management. Apache IvyDE will contribute to the classpath of your Java project or you can make it retrieve your dependencies directly into your project. Last but not least Apache IvyDE offer editors of ivy.xml and ivysettings.xml files with completion. Get some preview here: <a href="http://ant.apache.org/ivy/ivyde/screenshots.html">http://ant.apache.org/ivy/ivyde/screenshots.html</a>.<br class="xooki-br"/><br class="xooki-br"/><h1><a name="status"></a>Status of this release</h1>
-IvyDE has been maintained to be compatible with Eclipse 3.2, 3.3, 3.4 and 3.5.<br class="xooki-br"/><br class="xooki-br"/><h2>JVM compability</h2>
+This release contains sevral major improvements along with some bug fixes. The major<br class="xooki-br"/>improvements are about the resolve scheduler and how retrieved artifact are handled.<br class="xooki-br"/>Thus this release is considered as a beta one.<br class="xooki-br"/><br class="xooki-br"/><h1><a name="majorchanges"></a>Major Changes in this Release</h1>
-IvyDE has been kept compatible with Java 1.4.<br class="xooki-br"/><br class="xooki-br"/><hr/><div class='toc-title toc-title-2'>Installation</div><br class="xooki-br"/><h1><a name="latest"></a>Install the last release via Internet</h1>
+As for this release and the next ones, Apache IvyDE now expects to be installed in Eclipse 3.4 or superior.<br class="xooki-br"/><br class="xooki-br"/>Apache IvyDE has now a synchronous job to launch resolve of dependencies on the projets. So<br class="xooki-br"/>IvyDE will be able to order the resolve of the projects in the correct order regarding<br class="xooki-br"/>their inter dependencies. And the immediate effect is that Eclipse get notified only<br class="xooki-br"/>one time of a classpath change, and thus triggerin only one wrokspace build.<br class="xooki-br"/><br class="xooki-br"/>Apache IvyDE is now capable of having a classpath based on retrieved artifact rather than<br class="xooki-br"/>on the cached ones.<br class="xooki-br"/><br class="xooki-br"/>The existing retrieve configuration are now considered "standonale" ones, as they<br class="xooki-br"/>are independant of the classpath container. They can even now be part of non Java<br class="xooki-br"/>project.<br
class="xooki-br"/><br class="xooki-br"/><h1><a name="contrib"></a>Committers and Contributors for this Release</h1>
-For most user who have access to the internet it is simpler to install the latest release from the IvyDE updatesite. So just look out there:<br class="xooki-br"/><a href="http://ant.apache.org/ivy/ivyde/download.cgi">http://ant.apache.org/ivy/ivyde/download.cgi</a><br class="xooki-br"/><br class="xooki-br"/><h1><a name="manual"></a>Manual install</h1>
+Here is the list of people who have contributed source code and documentation<br class="xooki-br"/>to this release. Many thanks to all of them, and also to the whole IvyDE community<br class="xooki-br"/>contributing ideas and feedback, and promoting the use of Apache IvyDE. The list would be too<br class="xooki-br"/>long, but Apache IvyDE couldn't be what it is without you!<br class="xooki-br"/>
+<ul>Committers
+<li>Maarten Coene</li>
+<li>Xavier Hanin</li>
+<li>Nicolas Lalevée</li>
+<li>Jon Schneider</li>
+<li>Gilles Scokart</li>
+</ul>
+<ul>Contributors:
+<li>Clint Burghduff</li>
+<li>Gregory Fernandez</li>
+<li>Jeffrey M. Metcalf</li>
+</ul>
-<h2>Install IvyDE</h2>
+<h1><a name="changes"></a>List of Changes in this Release</h1>
-So you should have the zip distribution of IvyDE in which you should find these files:
+List of changes since <a href="/ivy/ivyde/history/2.1.0/release-notes.html">Apache IvyDE 2.1.0</a>:
+<ul>
+ <li>NEW: Custom color in XML editors (<a href="https://issues.apache.org/jira/browse/IVYDE-73">IVYDE-73</a>)</li>
+ <li>NEW: support for retrieve configuration in non Java project</li>
+ <li>NEW: an IvyDE classpath can now be retrieved (<a href="https://issues.apache.org/jira/browse/IVYDE-56">IVYDE-56</a>)</li>
+ <li>NEW: Add branch comparison to workspace resolver (<a href="https://issues.apache.org/jira/browse/IVYDE-234">IVYDE-234</a>) (thanks to Jeffrey M. Metcalf)</li>
+ <li>NEW: Look for ivysettings.xml file in project root copying the behavior of ivy ant task (<a href="https://issues.apache.org/jira/browse/IVYDE-258">IVYDE-258</a>)</li>
+ <li>NEW: IvyDE can now resolve in an offline mode, where Ivy use only the caches (Ivy 2.3 required)</li>
+ <li>NEW: Explicit ordering of configurations (<a href="https://issues.apache.org/jira/browse/IVYDE-159">IVYDE-159</a>)</li>
+ <li>NEW: Open the ivy file on the double click in the reverse dependency explorer</li>
+ <li>NEW: The ivysettings field editor now supports the variable ${ivyproject_loc} which is referencing the current project being resolved (<a href="https://issues.apache.org/jira/browse/IVYDE-247">IVYDE-247</a>)</li>
+</ul><ul>
+ <li>IMPROVE: let IvyDE refresh workspace after a resolve (<a href="https://issues.apache.org/jira/browse/IVYDE-27">IVYDE-27</a>) (thanks to Clint Burghduff)</li>
+ <li>IMPROVE: IvyDE now resolve by batch, then preventing too many workspace build (<a href="https://issues.apache.org/jira/browse/IVYDE-177">IVYDE-177</a>)</li>
+ <li>IMPROVE: Shared Javadoc/Source attachments (<a href="https://issues.apache.org/jira/browse/IVYDE-230">IVYDE-230</a>) (thanks to Gregory Fernandez)</li>
+ <li>IMPROVE: WorkspaceResolver: deal with self-dependencies (<a href="https://issues.apache.org/jira/browse/IVYDE-240">IVYDE-240</a>)</li>
+ <li>IMPROVE: Impossible to resolve dependencies: missing diagnostics (<a href="https://issues.apache.org/jira/browse/IVYDE-233">IVYDE-233</a>)</li>
+</ul><ul>
+ <li>FIX: Variable based path for ivysettings doesn't work it there are some spaces in the path (<a href="https://issues.apache.org/jira/browse/IVYDE-253">IVYDE-253</a>)</li>
+ <li>FIX: Triggers are not called (<a href="https://issues.apache.org/jira/browse/IVYDE-244">IVYDE-244</a>)</li>
+ <li>FIX: Missing ivysettings.xml can make the classpath container config to change (<a href="https://issues.apache.org/jira/browse/IVYDE-248">IVYDE-248</a>)</li>
+</ul>
+
+Most of our changes are logged in our JIRA, where you can find comments and links to our subversion:<br class="xooki-br"/><a href="https://issues.apache.org/jira/browse/ivyde">https://issues.apache.org/jira/browse/ivyde</a><br class="xooki-br"/><br class="xooki-br"/><hr/><div class='toc-title toc-title-2'>License</div><hr/><div class='toc-title toc-title-2'>Compatibility</div><br class="xooki-br"/><h2>Upgrading/Downgrading</h2>
+
+This version is compatible with every earlier Apache release (since 2.0.0.alpha1). Any upgrade of Apache IvyDE should work without any worries.<br class="xooki-br"/><br class="xooki-br"/>The reverse is not true, downgrading is not supported and may break your configuration<br class="xooki-br"/><br class="xooki-br"/><h2>Dependency on Apache Ivy</h2>
+
+Apache IvyDE expects to be used with a version 2.1 or superior of Apache Ivy.<br class="xooki-br"/><br class="xooki-br"/><h2>Eclipse™ integration</h2>
+
+Apache IvyDE has been maintained to be compatible with Eclipse 3.4, 3.5 and 3.6.<br class="xooki-br"/><br class="xooki-br"/><h2>JVM compability</h2>
+
+Apache IvyDE has been kept compatible with Java 1.4.<br class="xooki-br"/><br class="xooki-br"/><hr/><div class='toc-title toc-title-2'>Installation</div><br class="xooki-br"/><h1><a name="latest"></a>Install the last release via Internet</h1>
+
+For most user who have access to the internet it is simpler to install the latest release from the Apache IvyDE updatesite. So just look out there:<br class="xooki-br"/><a href="http://ant.apache.org/ivy/ivyde/download.cgi">http://ant.apache.org/ivy/ivyde/download.cgi</a><br class="xooki-br"/><br class="xooki-br"/><h1><a name="manual"></a>Manual install</h1>
+
+<h2>Install Apache IvyDE</h2>
+
+So you should have the zip distribution of Apache IvyDE in which you should find these files:
<ul>
<li>features/org.apache.ivyde.feature_2.1.0.XXXX.jar</li>
<li>plugins/org.apache.ivyde.eclipse_2.1.0.XXXX.jar</li>
@@ -80,9 +141,9 @@ You can then install them by copying the
cp features/* $ECLIPSE_HOME/features<br class="xooki-br"/>cp plugins/* $ECLIPSE_HOME/plugins
</pre>
-<h2>Install the latest Ivy bundle</h2>
+<h2>Install the latest Apache Ivy bundle</h2>
-Get the latest Ivy feature and bundle for the updatesite:
+Get the latest Apache Ivy feature and bundle for the updatesite:
<ul>
<li>the <a href="[preferred]/ant/ivyde/updatesite/features">features folder</a></li>
<li>the <a href="[preferred]/ant/ivyde/updatesite/plugins">plugins folder</a></li>
@@ -90,7 +151,7 @@ Get the latest Ivy feature and bundle fo
And then just copy them respectively in the $ECLIPSE_HOME/features and the $ECLIPSE_HOME/plugins folders.<br class="xooki-br"/><br class="xooki-br"/><h2>Restart Eclipse</h2>
-After installing manually your plugins, you have to restart your Eclipse to have it take into account the changes. It is recommended to restart it with the -clean option on the command line.<br class="xooki-br"/><br class="xooki-br"/><hr/><div class='toc-title toc-title-2'>Classpath Container</div><br class="xooki-br"/>The IvyDE classpath container will help you manage the classpath of your Eclipse projects, based on the dependencies declared in Ivy files found in your projects.<br class="xooki-br"/><br class="xooki-br"/>Some of the tasks that can be performed on the container include:
+After installing manually your plugins, you have to restart your Eclipse to have it take into account the changes. It is recommended to restart it with the -clean option on the command line.<br class="xooki-br"/><br class="xooki-br"/><hr/><div class='toc-title toc-title-2'>Classpath Container</div><br class="xooki-br"/>The IvyDE classpath container will help you manage the classpath of your Eclipse™ projects, based on the dependencies declared in Ivy files found in your projects.<br class="xooki-br"/><br class="xooki-br"/>Some of the tasks that can be performed on the container include:
<ul>
<li><a href="cpc/create.html">Create</a> a container</li>
<li><a href="cpc/edit.html">Edit</a> its setup</li>
@@ -105,7 +166,7 @@ After installing manually your plugins,
For most of the projects, the ivy.xml file (or the pom.xml) is in the java project. So you can just right click on the ivy.xml and select "Add Ivy Library..." and you can directly access the prefilled setup of the IvyDE classpath container<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/addivylibrary.jpg"></center>
<h1>Standard creation</h1>
-The standard way to add the IvyDE classpath container is to manipulate the Eclipse's "Build Path":
+The standard way to add the IvyDE classpath container is to manipulate the Eclipse™'s "Build Path":
<ul>
<li>Select the project in which you want to create an IvyDE classpath container and open the "Add Libraries" form of Eclipse (in package Explorer, in the context menu of your project choose : [Build Path]/[Add Libraries]).<br/><br/><center><img src="images/build_path_menu.jpg"/></center><br/><br/></li>
<li>Select the "IvyDE Managed Dependencies" item.<br/><br/><center><img src="images/add_lib.jpg"/></center><br/><br/></li>
@@ -115,12 +176,12 @@ The standard way to add the IvyDE classp
Now your classpath is set and you can see all dependencies in one unique folder of the package explorer (folder name = ivy-file-name[conf1,conf2]).<br class="xooki-br"/><br class="xooki-br"/><br class="xooki-br"/><center><img src="images/cp_node.jpg"></center>
-<hr/><div class='toc-title toc-title-3'>Edit the classpath</div><br class="xooki-br"/>During the life of your project, you can change the ivy.xml file or <a href="maven.html">maven pom.xml</a> and change its configuration.<br class="xooki-br"/><br class="xooki-br"/>These properties can be accessed by he context menu of the IvyDE classpath container:<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/cp_configuration.jpg"></center>
+<hr/><div class='toc-title toc-title-3'>Edit the classpath</div><br class="xooki-br"/>During the life of your project, you can change the ivy.xml file or <a href="maven.html">maven pom.xml</a> and change its configuration.<br class="xooki-br"/><br class="xooki-br"/>These properties can be accessed by the context menu of the IvyDE classpath container:<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/cp_configuration.jpg"></center>
You can also edit it via the build path configuration. Open the build path configuration dialog, select the "Libraries" panel and select the IvyDE classpath container. Then click on the "Edit" button: the IvyDE classpath container configuration dialog will pop up.<br class="xooki-br"/>This is particularly useful when Eclipse hides the empty classpath containers (since Eclipse 3.3). When the container is empty, this is the only way to trigger a resolve on this project.<br class="xooki-br"/><br/><br/>
<center><img src="images/build_path_edit.jpg"></center>
<br/>
-<hr/><div class='toc-title toc-title-3'>Launching resolve</div><br class="xooki-br"/>You can explicitly ask for Ivy dependency resolution from your classpath container.<br class="xooki-br"/><br class="xooki-br"/>This command will invoke the "resolve" ivy task and update your classpath container.<br class="xooki-br"/><br class="xooki-br"/>There is also a "refresh" action: this action is similar to the resolve one, but does not perform a full resolve if a report already exists in the cache. This is particularly useful if you work with Ant and a command line so that you avoid two full resolves. It is also the default action performed on classpath containers when the Eclipse workspace is opened (<b>Windows > Preferences > Ivy</b>), in effect restoring the classpath container to its state prior to the last closing of the workspace if no other action is performed against the ivy.xml in the meantime.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/cp_resolve.jp
g"></center><br/>
+<hr/><div class='toc-title toc-title-3'>Launching resolve</div><br class="xooki-br"/>You can explicitly ask for Ivy dependency resolution from your classpath container.<br class="xooki-br"/><br class="xooki-br"/>This command will invoke the "resolve" Ivy task and update your classpath container.<br class="xooki-br"/><br class="xooki-br"/>There is also a "refresh" action: this action is similar to the resolve one, but does not perform a full resolve if a report already exists in the cache. This is particularly useful if you work with Apache Ant and a command line so that you avoid two full resolves. It is also the default action performed on classpath containers when the Eclipse workspace is opened (<b>Windows > Preferences > Ivy</b>), in effect restoring the classpath container to its state prior to the last closing of the workspace if no other action is performed against the ivy.xml in the meantime.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/cp_res
olve.jpg"></center><br/>
You can also trigger a resolve (not a refresh!) of every IvyDE classpath container in the workspace via the button in the tool bar of Eclipse.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/resolveall.jpg"></center><br/>
@@ -133,9 +194,34 @@ And to launch a resolve on a specified s
<center><img src="images/resolve_contextmenu.jpg"></center><br/>
-<hr/><div class='toc-title toc-title-3'>Retrieve dependencies</div><br class="xooki-br"/>It is possible to make IvyDE copy resolved dependencies into your project: a retrieve of the dependencies can be triggered on each resolve of the classpath container.<br class="xooki-br"/><br class="xooki-br"/>To enable this behavior, enter the classpath container configuration panel, and select the second tab, "Retrieve".<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/retrieve.jpg"/></center>
+<hr/><div class='toc-title toc-title-3'>Retrieve dependencies</div><br class="xooki-br"/>It is possible to make Apache IvyDE copy resolved dependencies into your project: a retrieve of the dependencies can be triggered on each resolve of the classpath container.<br class="xooki-br"/><br class="xooki-br"/>To enable this behavior, enter the classpath container configuration panel, and select the second tab, "Retrieve".<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/retrieve.jpg"/></center>
+
+The <b>Retrieve pattern</b> specifies the location where the dependencies should be copied relative to the containing project.<br class="xooki-br"/><br class="xooki-br"/>The <b>Delete old retrieved artifacts</b> check box will cause IvyDE to clean the output directory before each retrieve. Note that any other artifacts other than those previously retrieved by IvyDE in this container will be deleted as well if this option is selected.<br class="xooki-br"/><br class="xooki-br"/>Finally, you can select which <b>Configurations</b> should be resolved and you can select which <b>Types</b> of artifacts should actually be retrieved. In both fields, <i>*</i> means <i>all</i>.<br class="xooki-br"/><br class="xooki-br"/><hr/><div class='toc-title toc-title-3'>Jar mapping</div><br class="xooki-br"/>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 whic
h contains javadocs. And also how to bind one on each other.<br class="xooki-br"/><br class="xooki-br"/><h1>Finding jars types</h1>
+
+There are three types of jars handled by Eclipse™:
+<ul>
+ <li>the binary jars: they will be added to the classpath in oder to compile and run; they contain the .class files.</li>
+ <li>the source jars/zip: they will be bound to the binary one to browse dependency sources; they are basically a zip of .java files</li>
+ <li>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 respectin a layout produced by javadoc.</li>
+</ul>
+
+To find the binary jars, Apache IvyDE is relying on the "Accepted types" preference field you can find in the <a href="create.html">container configuration panel</a>, or in the <a href="../preferences.html#classpath">global one</a>. If the artifact has a type listed here, it is then added to the classpath.<br class="xooki-br"/><br class="xooki-br"/>For the sources, it is relying on the "Sources types".<br class="xooki-br"/><br class="xooki-br"/>For the javadocs, it is relying on the "Javadocs types".<br class="xooki-br"/><br class="xooki-br"/><h1>Binding the jars</h1>
+
+The second step is to bind a source artifact with a binary one. Apache IvyDE has the folowing algorithm:
+<ul>
+ <li>first if a binary jar has the same artifact name than a source one, there are bound together.</li>
+ <li>if none matched, then IvyDE search for sources which have one of the suffix specified in "Sources suffixes".</li>
+</ul>
-The <b>Retrieve pattern</b> specifies the location where the dependencies should be copied relative to the containing project.<br class="xooki-br"/><br class="xooki-br"/>The <b>Delete old retrieved artifacts</b> check box will cause IvyDE to clean the output directory before each retrieve. Note that any other artifacts other than those previously retrieved by IvyDE in this container will be deleted as well if this option is selected.<br class="xooki-br"/><br class="xooki-br"/>Finally, you can select which <b>Configurations</b> should be resolved and you can select which <b>Types</b> of artifacts should actually be retrieved. In both fields, <i>*</i> means <i>all</i>.<br class="xooki-br"/><br class="xooki-br"/><hr/><div class='toc-title toc-title-3'>Clean the caches</div><br class="xooki-br"/>IvyDE has the ability to clean the various types of Ivy caches.<br class="xooki-br"/><br class="xooki-br"/>On a configured IvyDE classpath container, open the context menu and select th
e <b>Clean Ivy cache</b> entry. A menu of configured caches will be shown.<br class="xooki-br"/>
+For 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:
+<ul>
+<li>mylib.jar (type=source)</li>
+<li>mylib-source.jar (type=source)</li>
+<li>mylib-sources.jar (type=source)</li>
+<li>mylib-src.jar (type=source)</li>
+</ul>
+
+Note that Apache IvyDE don't care about the extension, it can be .zip too.<br class="xooki-br"/><br class="xooki-br"/>Same apply for javadocs with respectively "Javadocs suffixes".<hr/><div class='toc-title toc-title-3'>Clean the caches</div><br class="xooki-br"/>Apache IvyDE has the ability to clean the various types of Ivy caches.<br class="xooki-br"/><br class="xooki-br"/>On a configured IvyDE classpath container, open the context menu and select the <b>Clean Ivy cache</b> entry. A menu of configured caches will be shown.<br class="xooki-br"/>
<ul>
<li><u>All:</u> will clean every cache</li>
<li><u>Resolution cache:</u> will clean only the cache of the resolution report</li>
@@ -151,7 +237,7 @@ The <b>Retrieve pattern</b> specifies th
<li>Reloading the settings in a project will not make other projects reload their settings even if they use the same settings file</li>
</ul>
-<hr/><div class='toc-title toc-title-3'>Resolve in workspace</div><br class="xooki-br"/>Some projects are composed of mulpliple modules. Often, these modules have dependencies between them, dependencies managed by Ivy (of course!). <br class="xooki-br"/><br class="xooki-br"/>Eclipse is capable of calculating the workspace's build order according to dependencies between projects. To leverage this advantage, IvyDE has the ability to add a project reference to a dependency located in the workspace in place of downloading its published artifact(s) from the repository. In this way, developers can develop multi-module applications, and test the interaction between these modules, before building and publishing artifacts to the repository.<br class="xooki-br"/><br class="xooki-br"/>Consider a multi-module application with a considerable amount of code in each of several projects. Many developers have experienced the delays involved in waiting for Eclipse to build code across all
of these projects even though development is only being conducted in one isolated part of the application (maybe just one or two projects). If the latest published artifact in the Ivy repository has the same source code as a module that the developer is not currently working on, simply closing that project in the Eclipse workspace and resolving dependencies on dependent projects that would resolve that artifact speeds the compilation process considerably.<br class="xooki-br"/><br class="xooki-br"/>First, each application module should be separate a project in Eclipse, and each of these projects should have a configured IvyDE classpath container.<br class="xooki-br"/><br class="xooki-br"/>To enable resolution in the workspace, go to the advanced configuration panel of the classpath container and select <b>Resolve dependencies in workspace</b>.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/workspace.jpg"/></center>
+<hr/><div class='toc-title toc-title-3'>Resolve in workspace</div><br class="xooki-br"/>Some projects are composed of mulpliple modules. Often, these modules have dependencies between them, dependencies managed by Apache Ivy (of course!). <br class="xooki-br"/><br class="xooki-br"/>Eclipse is capable of calculating the workspace's build order according to dependencies between projects. To leverage this advantage, Apache IvyDE has the ability to add a project reference to a dependency located in the workspace in place of downloading its published artifact(s) from the repository. In this way, developers can develop multi-module applications, and test the interaction between these modules, before building and publishing artifacts to the repository.<br class="xooki-br"/><br class="xooki-br"/>Consider a multi-module application with a considerable amount of code in each of several projects. Many developers have experienced the delays involved in waiting for Eclipse™ to b
uild code across all of these projects even though development is only being conducted in one isolated part of the application (maybe just one or two projects). If the latest published artifact in the Ivy repository has the same source code as a module that the developer is not currently working on, simply closing that project in the Eclipse workspace and resolving dependencies on dependent projects that would resolve that artifact speeds the compilation process considerably.<br class="xooki-br"/><br class="xooki-br"/>First, each application module should be separate a project in Eclipse, and each of these projects should have a configured IvyDE classpath container.<br class="xooki-br"/><br class="xooki-br"/>To enable resolution in the workspace, go to the advanced configuration panel of the classpath container and select <b>Resolve dependencies in workspace</b>.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/workspace.jpg"/></center>
<u>Important notes:</u> to make the resolve in workspace work correctly the <i>info</i> in the ivy.xml should be properly set:
<ul>
@@ -176,6 +262,12 @@ Having two projects "A" and "B" configur
<tr><td>[1.2,1.3)</td><td>$version</td><td>no project wiring</td></tr>
</table>
+In some setup, if you want to mix some resolver of your own and the workspace resolver, and still want the transitive dependencies work nicely between them, you may want to turn the resolve mode to <a href="http://ant.apache.org/ivy/history/latest-milestone/use/resolve.html">dynamic</a>:
+<ul>
+ <li>see the defaultResolveMode attribute of <a href="http://ant.apache.org/ivy/history/latest-milestone/settings/settings.html">settings</a> in the ivysettings.</li>
+ <li>see the resolveMode attribute of <a href="http://ant.apache.org/ivy/history/latest-milestone/settings/module.html">module</a> in the ivysettings.</li>
+</ul>
+
<hr/><div class='toc-title toc-title-3'>Launch configuration</div><br class="xooki-br"/>The IvyDE classpath container can also be used in the launch configuration, run or debug.<br class="xooki-br"/><br class="xooki-br"/><h1>Default behavior</h1>
By default, the container will be used because it is included in the default classpath of you project. This is the configuration that you implicitly have when you do a "Run As..." on a Java class. The container you see in the launch classpath is the same as the one you have in your project in the package explorer.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/launch_default.jpg"></img></center>
@@ -195,7 +287,7 @@ Select the absolute path to your ivy.xml
Click "Finish" and see the result:<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/launch_custom.jpg"></img></center>
-<hr/><div class='toc-title toc-title-3'>Use with maven poms</div><br class="xooki-br"/>If you want to use a maven pom.xml instead of an ivy.xml file, you can select a pom file in the configuration options of the IvyDE classpath.<br class="xooki-br"/><br class="xooki-br"/>When a maven pom is selected, the configurations list is updated with all maven scopes.<br class="xooki-br"/><br class="xooki-br"/>Both examples below are a good illustration of the simplicity of using maven poms in IvyDE:
+<hr/><div class='toc-title toc-title-3'>Use with maven poms</div><br class="xooki-br"/>If you want to use a Apache Maven™ pom.xml instead of an ivy.xml file, you can select a pom file in the configuration options of the IvyDE classpath.<br class="xooki-br"/><br class="xooki-br"/>When a maven pom is selected, the configurations list is updated with all maven scopes.<br class="xooki-br"/><br class="xooki-br"/>Both examples below are a good illustration of the simplicity of using maven poms in Apache IvyDE:
<ul>
<li><a href="#one">Maven1 sample</a></li>
<li><a href="#two">Maven2 sample</a></li>
@@ -203,7 +295,7 @@ Click "Finish" and see the result:<br cl
<h1><a name="one"></a>Maven1 Sample</h1>
-This sample presents a simple use case involving a maven pom and the IvyDE classpath container. We are going to create an Eclipse project on commons-httpclient sources.<br class="xooki-br"/><br class="xooki-br"/><b> - Download the <a href="http://archive.apache.org/dist/httpcomponents/commons-httpclient/3.0/source/commons-httpclient-3.0-src.zip">commons httpclient sources</a></b><br class="xooki-br"/><br class="xooki-br"/><b> - Unzip this file (c:/tmp/commons-httpclient/)</b><br class="xooki-br"/><br class="xooki-br"/><b> - Create a new Eclipse java project based on the unzipped sources (c:/tmp/commons-httpclient/)</b><br class="xooki-br"/><br class="xooki-br"/><center>
+This sample presents a simple use case involving a maven pom and the IvyDE classpath container. We are going to create an Eclipse™ project on commons-httpclient sources.<br class="xooki-br"/><br class="xooki-br"/><b> - Download the <a href="http://archive.apache.org/dist/httpcomponents/commons-httpclient/3.0/source/commons-httpclient-3.0-src.zip">commons httpclient sources</a></b><br class="xooki-br"/><br class="xooki-br"/><b> - Unzip this file (c:/tmp/commons-httpclient/)</b><br class="xooki-br"/><br class="xooki-br"/><b> - Create a new Eclipse java project based on the unzipped sources (c:/tmp/commons-httpclient/)</b><br class="xooki-br"/><br class="xooki-br"/><center>
<img src="images/httpProject_errors.jpg"><br />
<u><b>Note:</b></u> your project willnot compile: some imports cannot be resolved.<br class="xooki-br"/></center>
@@ -218,11 +310,11 @@ This sample presents a simple use case i
<h1><a name="two"></a>Maven2 Sample</h1>
-This sample demonstrates how the IvyDE classpath container on a Maven2 pom can handle transitive dependencies.<br class="xooki-br"/><br class="xooki-br"/><b> - Create a new empty java project in Eclipse.</b><br class="xooki-br"/><br class="xooki-br"/><b> - In your project, create an <tt>ivysettings.xml</tt> file: </b><br class="xooki-br"/>
+This sample demonstrates how the IvyDE classpath container on a Apache Maven 2 pom can handle transitive dependencies.<br class="xooki-br"/><br class="xooki-br"/><b> - Create a new empty java project in Eclipse.</b><br class="xooki-br"/><br class="xooki-br"/><b> - In your project, create an <tt>ivysettings.xml</tt> file: </b><br class="xooki-br"/>
<pre><ivysettings><br class="xooki-br"/> <conf defaultResolver="ibiblio"/><br class="xooki-br"/> <resolvers><br class="xooki-br"/> <ibiblio name="ibiblio" /><br class="xooki-br"/> </resolvers><br class="xooki-br"/></ivysettings>
</pre>
-Using the m2compatible attribute, you can benefit from Maven2 repository compatibility.<br class="xooki-br"/><br class="xooki-br"/><b> - In your project, create a <tt>pom.xml</tt> file: </b><br class="xooki-br"/>
+Using the m2compatible attribute, you can benefit from Apache Maven 2 repository compatibility.<br class="xooki-br"/><br class="xooki-br"/><b> - In your project, create a <tt>pom.xml</tt> file: </b><br class="xooki-br"/>
<pre>
<project><br class="xooki-br"/> <modelVersion>4.0.0</modelVersion><br class="xooki-br"/> <groupId>com.mycompany</groupId><br class="xooki-br"/> <artifactId>myproject</artifactId><br class="xooki-br"/> <version>1.0-SNAPSHOT</version><br class="xooki-br"/> <dependencies><br class="xooki-br"/> <dependency><br class="xooki-br"/> <groupId>commons-httpclient</groupId><br class="xooki-br"/> <artifactId>commons-httpclient</artifactId><br class="xooki-br"/> <version>3.0</version><br class="xooki-br"/> </dependency><br class="xooki-br"/> </dependencies><br class="xooki-br"/></project>
</pre>
@@ -246,9 +338,9 @@ Using the m2compatible attribute, you ca
<b> - That's all! Your IvyDE classpath container resolves all dependencies including those that were transitive to the commons-httpclient module!</b><br class="xooki-br"/><br class="xooki-br"/><center>
<img src="images/maven2classpath2.jpg"/>
</center>
-<hr/><div class='toc-title toc-title-3'>WTP integration</div><br class="xooki-br"/>WTP refers to the <a href="http://www.eclipse.org/webtools/">Web Tools Platform</a> project from the Eclipse foundation which allows Eclipse users to easily develop, launch and debug web applications. IvyDE works with WTP 2.0+ (Eclipse 3.3+).<br class="xooki-br"/><br class="xooki-br"/>In the properties of your project configured to use WTP, there is a section titled "Java EE Module Dependencies". In this section you will find the IvyDE classpath container listed, usually with the name "ivy.xml [*]". Select it and dependencies found in the IvyDE classpath container will be deployed as well.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/wtp.jpg"/></center>
+<hr/><div class='toc-title toc-title-3'>WTP integration</div><br class="xooki-br"/>WTP refers to the <a href="http://www.eclipse.org/webtools/">Web Tools Platform</a> project from the Eclipse Foundation which allows Eclipse™ users to easily develop, launch and debug web applications. Apache IvyDE works with WTP 2.0+ (Eclipse 3.3+).<br class="xooki-br"/><br class="xooki-br"/>In the properties of your project configured to use WTP, there is a section titled "Java EE Module Dependencies". In this section you will find the IvyDE classpath container listed, usually with the name "ivy.xml [*]". Select it and dependencies found in the IvyDE classpath container will be deployed as well.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/wtp.jpg"/></center>
-This has been successfully tested with Eclipse 3.3/WTP 2.0, and Eclipse 3.4/WTP 3.0.<br class="xooki-br"/><br class="xooki-br"/><h1>IBM Rational Application Developer (RAD) 7.5.3+</h1>
+This has been successfully tested with Eclipse 3.3/WTP 2.0, and Eclipse 3.4/WTP 3.0.<br class="xooki-br"/><br class="xooki-br"/><h1>IBM™ Rational Application Developer (RAD™) 7.5.3+</h1>
Users of RAD 7.5.3 will notice that the classpath container is not listed in the table. RAD prevents the deployment of classpath containers by default. To allow this behavior, selection Windows > Preferences > Java EE. Check "Allow loose classpath module dependencies". RAD will present you with a warning message. To enable the behavior, you need to check the option again in the popup and click Yes.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/rad_jee_page.jpg"/></center>
<br/>
@@ -259,7 +351,7 @@ Users of RAD 7.5.3 will notice that the
<li>Load the modified .epf</li>
</ul>
-<hr/><div class='toc-title toc-title-2'>Ivy file editor</div><br class="xooki-br"/>IvyDE comes with an Ivy file editor that provides an editor that performs code completion for Ivy xml tags based on the real-time state of your repository. It also packs with an Ivy file creation wizard and HTML preview.<br class="xooki-br"/><br class="xooki-br"/><h1><a name="wizard"></a>Creation Wizard</h1>
+<hr/><div class='toc-title toc-title-2'>Ivy file editor</div><br class="xooki-br"/>Apache IvyDE comes with an Ivy file editor that provides an editor that performs code completion for Ivy xml tags based on the real-time state of your repository. It also packs with an Ivy file creation wizard and HTML preview.<br class="xooki-br"/><br class="xooki-br"/><h1><a name="wizard"></a>Creation Wizard</h1>
To use the creation wizard, choose File > New > Other > IvyDE > Ivy file in the Eclipse menu (Ctrl+N by default). Select it and click Next.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/wizard1.jpg"/></center>
@@ -276,7 +368,7 @@ The wizard contains only one page, and i
<center><img src="images/editor1.jpg"/></center>
-IvyDE's Eclipse editor provides XML syntax coloration, tag completion, tag attribute name completion, and dependency and configuration tag value completion.<br class="xooki-br"/><br class="xooki-br"/>Completion comes with contextual help. The completion popup is displayed when through the CTRL + SPACE shortcut.<br class="xooki-br"/><br class="xooki-br"/><b>Available completions:</b><ul>
+Apache IvyDE's Eclipse editor provides XML syntax coloration, tag completion, tag attribute name completion, and dependency and configuration tag value completion.<br class="xooki-br"/><br class="xooki-br"/>Completion comes with contextual help. The completion popup is displayed when through the CTRL + SPACE shortcut.<br class="xooki-br"/><br class="xooki-br"/><b>Available completions:</b><ul>
<li><b>XML structure</b>: Allows you quickly to insert valid tags at the right place. If the tag can have nested children, both notations, simple tag and open tag, are proposed.<br class="xooki-br"/> <br class="xooki-br"/> <center><img src="images/completion1.jpg"/></center>
</li>
@@ -298,7 +390,7 @@ IvyDE's Eclipse editor provides XML synt
</li>
</ul>
-<hr/><div class='toc-title toc-title-2'>Ivy settings editor</div><br class="xooki-br"/>IvyDE provides an editor of ivysettings.xml files. It provides completion on all tag and attribute names.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/settings.jpg"/></center>
+<b>Change colors:</b> you can change the color used by the editor in the <a href="preferences.html#xmleditor">global preferences page</a>.<br class="xooki-br"/><br class="xooki-br"/><hr/><div class='toc-title toc-title-2'>Ivy settings editor</div><br class="xooki-br"/>IvyDE provides an editor of ivysettings.xml files. It provides completion on all tag and attribute names.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/settings.jpg"/></center>
Completion comes with contextual help. The completion popup is displayed through the CTRL + SPACE shortcut.<br class="xooki-br"/><br class="xooki-br"/><b>Available completions:</b><ul>
<li><b>XML structure</b>: Allows you to quickly to insert valid tags in the right place. If the tag can have nested childrenm, both notations, simple tag and open tag, are proposed.<br class="xooki-br"/> <br class="xooki-br"/> <center><img src="images/settings_completion_struct.jpg"/></center> </li>
@@ -306,12 +398,13 @@ Completion comes with contextual help. T
</li>
</ul>
-<hr/><div class='toc-title toc-title-2'>Eclipse global preferences</div><br class="xooki-br"/>IvyDE maintains a global configuration, which controls the behaviour of every Ivy instance in every project in the workspace. This global configuration can be overrided in each <a href="cpc/edit.html">project</a>.<br class="xooki-br"/><br class="xooki-br"/>The global configuration can be found in the preferences of Eclipse (menu Window > Preferences for Windows and Linux users, Eclipse > Preferences for mac users), and select the item Ivy.<br class="xooki-br"/><br class="xooki-br"/><h1><a name="global"></a>Global Ivy preferences</h1>
-<center><img src="images/pref.jpg"/></center>
+<b>Change colors:</b> you can change the color used by the editor in the <a href="preferences.html#xmleditor">global preferences page</a>.<br class="xooki-br"/><br class="xooki-br"/><hr/><div class='toc-title toc-title-2'>Eclipse global preferences</div><br class="xooki-br"/>Apache IvyDE maintains a global configuration, which controls the behaviour of every Ivy instance in every project in the workspace. This global configuration can be overrided in each <a href="cpc/edit.html">project</a>.<br class="xooki-br"/><br class="xooki-br"/>The global configuration can be found in the preferences of Eclipse (menu Window > Preferences for Windows and Linux users, Eclipse > Preferences for mac users), and select the item Ivy.<br class="xooki-br"/><br class="xooki-br"/><h1><a name="global"></a>Global Ivy preferences</h1>
+
+<b><font color="red">TODO: SCREENSHOT NOT UP TO DATE</font></b><br class="xooki-br"/><center><img src="images/pref.jpg"/></center>
<ul>
- <li><u>On Eclipse startup:</u> Specifies what IvyDE should do in every project containing an IvyDE managed classpath container when Eclipse is starting up.</li>
+ <li><u>On Eclipse startup:</u> Specifies what Apache IvyDE should do in every project containing an IvyDE managed classpath container when Eclipse™ is starting up.</li>
<li><u>On Ivy file change:</u> Controls whether a resolve is performed each time Eclipse detects a change on an ivy.xml file configured by an IvyDE container via a save in the editor, a refresh, or a team/update.</li>
<li><u>Organisation:</u> Your company name for Ivy editor completion. </li>
<li><u>Organisation URL:</u> Your company web site url for Ivy editor completion.</li>
@@ -319,10 +412,10 @@ Completion comes with contextual help. T
<h1><a name="classpath"></a>Classpath configuration</h1>
-<center><img src="images/pref_classpath.jpg"/></center>
+<b><font color="red">TODO: SCREENSHOT NOT UP TO DATE</font></b><br class="xooki-br"/><center><img src="images/pref_classpath.jpg"/></center>
<ul>
- <li><u>Resolve dependencies in workpace:</u> IvyDE allows Ivy dependencies between projects in the workspace to be realized through project references rather than jars from the repository. See the <a href="cpc/workspace.html">documentation</a> for further information on this feature.</li>
+ <li><u>Resolve dependencies in workpace:</u> Apache IvyDE allows Ivy dependencies between projects in the workspace to be realized through project references rather than jars from the repository. See the <a href="cpc/workspace.html">documentation</a> for further information on this feature.</li>
<li><u>Resolve before launch:</u> an IvyDE container can be used in the classpath of a launch configuration, and the container can be resolved on each launch. See the documentation about <a href="cpc/launch.html">launch configurations</a> for further information on this feature.</li>
<li><u>Order of the classpath entries:</u> By default, the classpath container entries are ordered by order of declaration in the ivy.xml. When there are many entries, it can be useful to have them ordered lexically for enhanced readability.</li>
<li><u>Accepted types:</u> A comma separated list of extensions which will make IvyDE add the artifact to the classpath</li>
@@ -334,7 +427,7 @@ Completion comes with contextual help. T
<h1><a name="retrieve"></a>Retrieve setup</h1>
-<center><img src="images/pref_retrieve.jpg"/></center>
+<b><font color="red">TODO: SCREENSHOT NOT UP TO DATE</font></b><br class="xooki-br"/><center><img src="images/pref_retrieve.jpg"/></center>
<ul>
If checked, a retrieve job will be triggered after each the resolve.<br/>
@@ -346,17 +439,17 @@ Completion comes with contextual help. T
<h1><a name="settings"></a>Ivy settings</h1>
-<center><img src="images/pref_settings.jpg"/></center>
+<b><font color="red">TODO: SCREENSHOT NOT UP TO DATE</font></b><br class="xooki-br"/><center><img src="images/pref_settings.jpg"/></center>
<ul>
- <li><u>Reload the settings only on demand:</u> By default, IvyDE will parse the ivy settings file each times it is needed (each resolve, refresh, clean cache or completion in the ivy editor). For remote ivysettings this can slow the UI dramatically, so it is possible to make IvyDE keep the settings in a cache and only reload them via the context menu on the container).</li>
+ <li><u>Reload the settings only on demand:</u> By default, Apache IvyDE will parse the ivy settings file each times it is needed (each resolve, refresh, clean cache or completion in the ivy editor). For remote ivysettings this can slow the UI dramatically, so it is possible to make IvyDE keep the settings in a cache and only reload them via the context menu on the container).</li>
<li><u>Ivy settings path:</u> The path to your ivy settings file. Leave it blank to use Ivy default resolvers. See also the documentation about <a href="eclipsevar.html">Eclipse variables</a>.</li>
<li><u>Property files:</u> This is a comma separated list of Java properties files to be loaded along with the settings.</li>
</ul>
<h1><a name="workspace"></a>Workspace resolver</h1>
-<center><img src="images/pref_workspace.jpg"/></center>
+<b><font color="red">TODO: SCREENSHOT NOT UP TO DATE</font></b><br class="xooki-br"/><center><img src="images/pref_workspace.jpg"/></center>
<ul>
<li><u>Closing trigger resolve:</u> Closing a project which has the workspace resolver enabled will trigger a resolve on every project that depends on it.</li>
@@ -364,14 +457,17 @@ Completion comes with contextual help. T
<li><u>Ignore version when resolving workspace projects:</u> This option forces the workspace resolver to ignore the version of a module specified in an ivy.xml if a project containing an Ivy file with that module organization and name is found in the workspace, instead substituting a project reference. This may have unintended consequences.</li>
</ul>
+<h1><a name="xmleditor"></a>XML Editor</h1>
+
+<b><font color="red">TODO: SCREENSHOT</font></b><br class="xooki-br"/><center><img src="images/xmleditor_color_config.jpg"/></center>
-<hr/><div class='toc-title toc-title-2'>Eclipse variables</div><br class="xooki-br"/>Eclipse contains a <a href="http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-string_substitution.htm">string substitution mecanism</a>. This feature allows you to specify a path location that can be shared between developers.<br class="xooki-br"/><br class="xooki-br"/>IvyDE uses it to find the ivysettings.xml and properties files in both the <a href="preferences.html#settings">glogal preference page</a> and the <a href="cpc/create.html#localconf">project specific preference page</a>.<br class="xooki-br"/><br class="xooki-br"/>Using the "Workspace..." button will open a window to choose a file in the workspace. IvyDE will automatically fill the field with the proper variable.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/eclipsevar_workspace.jpg" /></center>
+This configuration panel allow you to change the color used in the <a href="ivyeditor.html">Ivy file editor</a> and the <a href="settingseditor.html">Ivy settings editor</a>.<br class="xooki-br"/><hr/><div class='toc-title toc-title-2'>Eclipse variables</div><br class="xooki-br"/>Eclipse contains a <a href="http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-string_substitution.htm">string substitution mecanism</a>. This feature allows you to specify a path location that can be shared between developers.<br class="xooki-br"/><br class="xooki-br"/>Apache IvyDE uses it to find the ivysettings.xml and properties files in both the <a href="preferences.html#settings">glogal preference page</a> and the <a href="cpc/create.html#localconf">project specific preference page</a>.<br class="xooki-br"/><br class="xooki-br"/>Using the "Workspace..." button will open a window to choose a file in the workspace. Apache IvyDE will auto
matically fill the field with the proper variable.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/eclipsevar_workspace.jpg" /></center>
Using the "File System..." button will allow you to choose a file in the file system. This path will not be portable.<br class="xooki-br"/><br class="xooki-br"/>Finally, you can choose to depend on the Eclipse variable system by clicking on "Variable...".<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/eclipsevar_variables.jpg" /></center>
-<b>Backwards compatibility</b><br class="xooki-br"/><br class="xooki-br"/>Previously, IvyDE supported the <tt>project://projectName/path/to/file.ext</tt> protocol. It sill does, but references of this style will be automatically converted in the saved settings to the Eclipse variable way of defining this path: <tt>${workspace_loc:projectName/path/to/file.ext}.</tt>
+<b>Backwards compatibility</b><br class="xooki-br"/><br class="xooki-br"/>Previously, Apache IvyDE supported the <tt>project://projectName/path/to/file.ext</tt> protocol. It sill does, but references of this style will be automatically converted in the saved settings to the Eclipse variable way of defining this path: <tt>${workspace_loc:projectName/path/to/file.ext}.</tt>
-<hr/><div class='toc-title toc-title-2'>Ivy Console</div><br class="xooki-br"/>The Ivy console provides the Ivy working traces that are visible in the command console. This view can be useful for understanding what Ivy and IvyDE are doing under the covers.<br/>
+<hr/><div class='toc-title toc-title-2'>Ivy Console</div><br class="xooki-br"/>The Ivy console provides the Ivy working traces that are visible in the command console. This view can be useful for understanding what Apache Ivy and Apache IvyDE are doing under the covers.<br/>
The Ivy Console can be accessed within your Eclipse Console view, by selecting the "Ivy Console" item.<br/>
<br/>
@@ -388,10 +484,10 @@ The colors in the console correspond to
To change the level of logging in the console, use the button in the view:<br class="xooki-br"/><br/>
<center><img src="images/ivy_console_debug.jpg"></center><br/>
-<hr/><div class='toc-title toc-title-2'>Eclipse's Ant integration</div><br class="xooki-br"/>Most Eclipse distributions include a plugin to launch Ant build files. The provided Ant distribution is a standard distribution of Ant that doesn't include Ivy. You may wish to run Ivy targets against Eclipse's Ant distribution.<br class="xooki-br"/><br class="xooki-br"/><h1>Configure Ant classpath</h1>
-For now, IvyDE doesn't contribute to the Ant classpath of the Eclipse plugin, so you will have to do it manually.<br class="xooki-br"/><br class="xooki-br"/>In the global preference page of the Ant runtime, click on <b>Add External JARs...</b><br class="xooki-br"/><br class="xooki-br"/><center><img src="images/antpref.jpg" /></center>
+<hr/><div class='toc-title toc-title-2'>Eclipse's Ant integration</div><br class="xooki-br"/>Most Eclipse™ distributions include a plugin to launch Apache Ant build files. The provided Apache Ant distribution is a standard distribution of Ant that doesn't include Apache Ivy. You may wish to run Ivy targets against Eclipse's Ant distribution.<br class="xooki-br"/><br class="xooki-br"/><h1>Configure Ant classpath</h1>
+For now, Apache IvyDE doesn't contribute to the Ant classpath of the Eclipse plugin, so you will have to do it manually.<br class="xooki-br"/><br class="xooki-br"/>In the global preference page of the Ant runtime, click on <b>Add External JARs...</b><br class="xooki-br"/><br class="xooki-br"/><center><img src="images/antpref.jpg" /></center>
-Then browse your filesystem to the <tt>plugins</tt> directory of your Eclipse installation and select the Ivy jar named <tt>org.apache.ivy_2.X.X.XXXXXXXXX.jar</tt>. Now Ivy has been added to the classpath of the Ant distribution embedded in Eclipse.<br class="xooki-br"/><br class="xooki-br"/><h1>Run Ivy targets</h1>
+Then browse your filesystem to the <tt>plugins</tt> directory of your Eclipse installation and select the Ivy jar named <tt>org.apache.ivy_2.X.X.XXXXXXXXX.jar</tt>. Now Ivy has been added to the classpath of the Ant distribution embedded in Eclipse.<br class="xooki-br"/><br class="xooki-br"/><h1>Run Apache Ivy targets</h1>
Create an Ant build file and declare the Ivy targets with:
<pre>
@@ -403,7 +499,7 @@ The build will now be successful:<br cla
<hr/><div class='toc-title toc-title-2'>Reverse Dependency Explorer</div><br class="xooki-br"/><h1>Introduction</h1>
-When working with multiple projects in a workspace that represent the whole or part of a larger application, you may want to simultaneously change the revisions of dependencies in several Ivy files to a single new revision all at the same time (notwithstanding the eviction mechanism inherent to Ivy). <br class="xooki-br"/><br class="xooki-br"/>At other times it is instructive just to see what dependencies are being utilized by projects in the workspace by revision without having to dig into each project and look at each individual module descriptor.<br class="xooki-br"/><br class="xooki-br"/>The Reverse Dependency Explorer turns the dependency tree upside-down, exploring the workspace by organization, module, and revision and providing a mechanism to synchronize revisions across projects/classpath containers.<br class="xooki-br"/><br class="xooki-br"/>Consider the following workspace, with three projects, all of which have an ivy.xml file at their project root. Each of thes
e Ivy files has an associated IvyDE managed classpath container.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/revexplorer_project.jpg"></center><br/>
+When working with multiple projects in a workspace that represent the whole or part of a larger application, you may want to simultaneously change the revisions of dependencies in several Ivy files to a single new revision all at the same time (notwithstanding the eviction mechanism inherent to Apache Ivy). <br class="xooki-br"/><br class="xooki-br"/>At other times it is instructive just to see what dependencies are being utilized by projects in the workspace by revision without having to dig into each project and look at each individual module descriptor.<br class="xooki-br"/><br class="xooki-br"/>The Reverse Dependency Explorer turns the dependency tree upside-down, exploring the workspace by organization, module, and revision and providing a mechanism to synchronize revisions across projects/classpath containers.<br class="xooki-br"/><br class="xooki-br"/>Consider the following workspace, with three projects, all of which have an ivy.xml file at their project root. Each
of these Ivy files has an associated IvyDE managed classpath container.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/revexplorer_project.jpg"></center><br/>
Right clicking on any (or all) of the projects and selecting Ivy > Reverse Dependency Explorer opens the view. The explorer displays a tree structure with an item for each organization/module pair. The third column lists all of the revisions of this pair for the selected projects. Expanding a tree item, you can see the module revision that a given Ivy classpath container depends on (if at all). Note that the view only shows direct dependencies and <i>no transitive dependencies</i>.<br class="xooki-br"/><br class="xooki-br"/><center><img src="images/revexplorer_view.jpg"></center><br/>
@@ -414,10 +510,10 @@ To synchronize revisions, click in the c
<hr/><div class='toc-title toc-title-2'>Developer doc</div><br class="xooki-br"/>Adding new features or fixing bugs needs community involvement.<br class="xooki-br"/>Here you will find the basics for how to get involved:
<ul>
-<li>How to <a href="dev/build.html">build</a> IvyDE from the sources</li>
-<li>and the process to de a <a href="dev/release.html">release</a> of IvyDE</li>
+<li>How to <a href="dev/build.html">build</a> Apache IvyDE from the sources</li>
+<li>and the process to de a <a href="dev/release.html">release</a> of Apache IvyDE</li>
</ul>
-<hr/><div class='toc-title toc-title-3'>Building</div><br class="xooki-br"/>This page describes how to build the IvyDE plugin from the source. The build is based on the Eclipse build system so it requires an Eclipse install. You also need to have an Ivy bundle installed.<br class="xooki-br"/><br class="xooki-br"/><h1><a name="setup"></a>Setup of the build</h1>
+<hr/><div class='toc-title toc-title-3'>Building</div><br class="xooki-br"/>This page describes how to build the Apache IvyDE plugin from the source. The build is based on the Eclipse™ build system so it requires an Eclipse install. You also need to have an Ivy bundle installed.<br class="xooki-br"/><br class="xooki-br"/><h1><a name="setup"></a>Setup of the build</h1>
<h2><a name="eclipse-install"></a>Eclipse installation</h2>
@@ -426,9 +522,9 @@ You need first an Eclipse install which
baseLocation=/home/me/tools/eclipse-3.4
</pre>
-<h2><a name="install-ivy"></a>The Ivy bundle</h2>
+<h2><a name="install-ivy"></a>The Apache Ivy bundle</h2>
-The IvyDE plugins depends on the Ivy 2.0 OSGi bundle. So the Ivy bundle have to be installed in the Eclipse installation before starting the build. An ant target will accomplished that task quite automatically. Inline help will be displayed when no property is specified:
+The IvyDE plugins depends on the Apache Ivy 2.0 OSGi bundle. So the Ivy bundle have to be installed in the Eclipse installation before starting the build. An Ant target will accomplished that task quite automatically. Inline help will be displayed when no property is specified:
<pre>ant install-ivy</pre>
<u>Note</u>: due to <a href="https://issues.apache.org/jira/browse/IVY-802">an old bug in the build script of Ivy</a>, the OSGi version of Ivy is "0.0.0" for every version older than the 2.0.0-RC1. So older version than 2.0.0-RC1 is not supported.<br class="xooki-br"/><br class="xooki-br"/><h1><a name="build"></a>Building</h1>
@@ -447,11 +543,13 @@ After a successful build you should have
cd $ECLIPSE_HOME<br class="xooki-br"/>unzip ...../dist/org.apache.ivyde.feature-$VERSION.zip
</pre>
-Then start your Eclipse and enjoy !<br class="xooki-br"/><hr/><div class='toc-title toc-title-3'>Releasing</div><br class="xooki-br"/>This documentation is defining every steps that needs to be accomplished when releasing IvyDE.<br class="xooki-br"/>In this doc, the released version is denoted as $VERSION, so it HAVE to be replaced in the command line argument accordingly. There is also some $LOGIN which is referencing your login on the Apache machines.<br class="xooki-br"/><br class="xooki-br"/><h1>Prepare</h1>
+Then start your Eclipse and enjoy !<br class="xooki-br"/><hr/><div class='toc-title toc-title-3'>Releasing</div><br class="xooki-br"/>This documentation is defining every steps that needs to be accomplished when releasing Apache IvyDE.<br class="xooki-br"/>In this doc, the released version is denoted as $VERSION, so it HAVE to be replaced in the command line argument accordingly. There is also some $LOGIN which is referencing your login on the Apache machines.<br class="xooki-br"/><br class="xooki-br"/><h1>Prepare</h1>
<h2>Jira</h2>
-First in <a href="https://issues.apache.org/jira/browse/IVYDE">Jira</a> make sure that no more issues are opened for the target release.<br class="xooki-br"/><br class="xooki-br"/><h2>Release branch</h2>
+First in <a href="https://issues.apache.org/jira/browse/IVYDE">Jira</a> make sure that no more issues are opened for the target release.<br class="xooki-br"/><br class="xooki-br"/><h2>Release notes</h2>
+
+Make sure the release notes and the annoucement are up to date. Look at doc/release-notes.html.<br class="xooki-br"/><br class="xooki-br"/><h2>Release branch</h2>
Some modifications of the branch are need to do the release. So a new branch is needed:
<pre>
@@ -471,24 +569,10 @@ The documentation have to specify the co
</ul>
The header should look like this
<pre>
-<title>${title} | IvyDE $VERSION Documentation</title>
+<title>${title} | Apache IvyDE $VERSION Documentation</title>
</pre>
-<h2>Release notes</h2>
-
-Go edit the RELEASE_NOTES.txt files. There are two things to change, marked by some <tt>TODO WHEN RELEASING</tt>:
-<ul>
- <li>the list of contributors should be filled according to the "thanks to" in the CHANGE.txt file</li>
- <li>the list of bug/features fixed in the release should be filled from the one in the CHANGE.txt file</li>
-</ul>
-
-Edit the IvyDE doc and add a new page just under the root of the documentation tree:
-<ul>
- <li>Child page title: Release Notes</li>
- <li>Child page path: release-notes</li>
-</ul>
-
-As content in that doc, copy paste the content of the RELEASE_NOTES.txt file.<br class="xooki-br"/>Then you should improve the style of the page by adding some h1, h2, remove unwanted line break. Normally you shouldn't care about the http link or the jira issue, xooki will take care of them.<br class="xooki-br"/><br class="xooki-br"/><h2>Commit your change</h2>
+<h2>Commit your changes</h2>
Don't forget to commit the changes you've done into the release branch.<br class="xooki-br"/><br class="xooki-br"/><h1>Building</h1>
@@ -517,7 +601,7 @@ And then the copy:
<pre>scp dist/* $LOGIN@people.apache.org:/home/$LOGIN/public_html/ivyde-$VERSION/</pre>
It is recommended to also deploy a staging updatesite there. See <a href="http://ant.apache.org/ivy/history/trunk/dev/updatesite.html">that page</a> to know how to proceed.<br class="xooki-br"/><br class="xooki-br"/>And launch the vote on the ant-dev mailing list:
<pre>
-Subject: [VOTE] IvyDE $VERSION Release<br class="xooki-br"/><br class="xooki-br"/>I have built a release candidate for IvyDE $VERSION<br class="xooki-br"/><br class="xooki-br"/>You can download the distribution from this URL: <a href="http://people.apache.org/~$LOGIN/ivyde-$VERSION/">http://people.apache.org/~$LOGIN/ivyde-$VERSION/</a><br class="xooki-br"/><br class="xooki-br"/>And a staging update site has been setup there: <a href="http://people.apache.org/~$LOGIN/staging/updatesite">http://people.apache.org/~$LOGIN/staging/updatesite</a><br class="xooki-br"/><br class="xooki-br"/>Do you vote for the release of these binaries?<br class="xooki-br"/><br class="xooki-br"/>[ ] Yes<br class="xooki-br"/>[ ] No<br class="xooki-br"/><br class="xooki-br"/>Regards,<br class="xooki-br"/><br class="xooki-br"/>$ME, IvyDE $VERSION release manager
+Subject: [VOTE] IvyDE $VERSION Release<br class="xooki-br"/><br class="xooki-br"/>I have built a release candidate for Apache IvyDE $VERSION<br class="xooki-br"/><br class="xooki-br"/>You can download the distribution from this URL: <a href="http://people.apache.org/~$LOGIN/ivyde-$VERSION/">http://people.apache.org/~$LOGIN/ivyde-$VERSION/</a><br class="xooki-br"/><br class="xooki-br"/>And a staging update site has been setup there: <a href="http://people.apache.org/~$LOGIN/staging/updatesite">http://people.apache.org/~$LOGIN/staging/updatesite</a><br class="xooki-br"/><br class="xooki-br"/>Do you vote for the release of these binaries?<br class="xooki-br"/><br class="xooki-br"/>[ ] Yes<br class="xooki-br"/>[ ] No<br class="xooki-br"/><br class="xooki-br"/>Regards,<br class="xooki-br"/><br class="xooki-br"/>$ME, IvyDE $VERSION release manager
</pre>
Note: this <a href="http://ant.apache.org/bylaws.html">page</a> is defining when and how a release can be accepted.<br class="xooki-br"/><br class="xooki-br"/><h1>Deployment</h1>
@@ -531,7 +615,9 @@ cp -R ~/public_html/ivyde-$VERSION /www/
<h2>Deploy the updatesite</h2>
-Follow the instructions of that page: <a href="http://ant.apache.org/ivy/history/latest-milestone/dev/updatesite.html#deployment">http://ant.apache.org/ivy/history/latest-milestone/dev/updatesite.html#deployment</a><br class="xooki-br"/><br class="xooki-br"/><h1>Update the documentation</h1>
+Follow the instructions of that page: <a href="http://ant.apache.org/ivy/history/latest-milestone/dev/updatesite.html#deployment">http://ant.apache.org/ivy/history/latest-milestone/dev/updatesite.html#deployment</a><br class="xooki-br"/><br class="xooki-br"/><h1>Annoucement</h1>
+
+The annoucement should have been already prepared and reviewed by other committers. Its content can be found in doc/release-notes.html.<br class="xooki-br"/><br class="xooki-br"/>With that content, send a mail to announce@apache.org, ivy-user@ant.apache.org and dev@ant.apache.org with the title "[ANNOUNCE] Apache IvyDE $VERSION released", and with your apache email as sender (announce@ requires it). <br class="xooki-br"/><br class="xooki-br"/><h1>Update the documentation</h1>
<h2>Update the table of content</h2>
@@ -588,8 +674,26 @@ Update the versions needs to be updated
<li>org.apache.ivyde.feature/feature.xml</li>
</ul>
+<h2>Clean up the release notes</h2>
+
+Edit the release notes in the documentation (doc/release-notes.html) so it can be prepared and maintanined for the next release:
+<ul>
+ <li>edit the content under "Release Annoucement": edit the version it is talking about and clean it up so it is a summary of the release notes</li>
+ <li>edit the content under "Status of this release": update it with the goal of the next release, or a TODO if it has not yet been defined</li>
+ <li>edit the content under "Major Changes in this Release": wipe it all and put there something like "Nothing done yet"</li>
+ <li>edit the content under "List of Changes in this Release": remove the list of entries and update the version in "List of changes since Apache IvyDE X.X.X"</li>
+</ul>
+
</div><!-- main -->
+<div id="footer-message" class="footer">
+ <hr />
+ <i>Copyright © 2010 The Apache Software Foundation, Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0.txt">Apache License, Version 2.0</a>.</i><br />
+ <i>Apache IvyDE, Apache Ivy, Apache Ant, IvyDE, Ivy, Ant, Apache, the Apache IvyDE logo, the Apache Ivy logo, the Apache Ant logo and the Apache feather logo are trademarks of The Apache Software Foundation.</i><br />
+ <i>Eclipse and the Eclipse logo are trademarks of Eclipse Foundation, Inc.</i>
+ <i>All other marks mentioned may be trademarks or registered trademarks of their respective owners. </i>
+</div>
+
</div><!-- body -->
</body>
</html>
Modified: ant/ivy/site/target/ivyde/history/trunk/compatibility.html
URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/trunk/compatibility.html?rev=1042869&r1=1042868&r2=1042869&view=diff
==============================================================================
--- ant/ivy/site/target/ivyde/history/trunk/compatibility.html (original)
+++ ant/ivy/site/target/ivyde/history/trunk/compatibility.html Tue Dec 7 00:00:26 2010
@@ -23,7 +23,7 @@
<script type="text/javascript">var xookiConfig = {level: 0};</script>
-<title>Compatibility | IvyDE</title>
+<title>Compatibility | Apache IvyDE™</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" type="text/css" href="style/style.css" />
<script src="js/jquery.pack.js" type="text/javascript"></script>
@@ -41,11 +41,11 @@
cellpadding="0" cellspacing="0" width="100%">
<tr>
<td id="home" width="30%"><a href="http://ant.apache.org/"
- title="Apache Ant"><img src="images/ant-group-logo.gif" alt="Apache Ant"
+ title="Apache Ant™"><img src="images/ant-group-logo.gif" alt="Apache Ant™"
border="0" /></a></td>
<td class="product" width="70%" align="right" valign="middle"><img
- src="images/logo.png" alt="IvyDE" border="0" /></td>
+ src="images/logo.png" alt="Apache IvyDE™" border="0" /></td>
</tr>
</table>
@@ -55,7 +55,7 @@
<td>
<div id="navcontainer">
- <a href="http://ant.apache.org/">Apache Ant</a> > <a href="http://ant.apache.org/ivy/">Ivy</a> > <a href="http://ant.apache.org/ivy/ivyde/">IvyDE</a> > <a href="http://ant.apache.org/ivy/ivyde/history.html">History</a> > <span class="breadCrumb"><a href="index.html" >Documentation (trunk)</a> > <a href="compatibility.html" class="current">Compatibility</a></span>
+ <a href="http://www.apache.org/">Apache™</a> > <a href="http://ant.apache.org/">Apache Ant™</a> > <a href="http://ant.apache.org/ivy/">Apache Ivy™</a> > <a href="http://ant.apache.org/ivy/ivyde/">Apache IvyDE™</a> > <a href="http://ant.apache.org/ivy/ivyde/history.html">History</a> > <span class="breadCrumb"><a href="index.html" >Documentation (trunk)</a> > <a href="compatibility.html" class="current">Compatibility</a></span>
</div>
</td>
</tr>
@@ -67,9 +67,9 @@
<tr>
<td id="sidebar-left">
<div class="block block-book" id="block-book-0">
- <h2>IvyDE</h2>
+ <h2>Apache IvyDE™</h2>
- <div class="content"><ul id="treemenu" class="treeview"><li id="xooki-index" class="submenu"><a href="index.html" >Documentation (trunk)</a><ul class="open"><li id="xooki-compatibility"><a href="compatibility.html" class="current">Compatibility</a></li><li id="xooki-install"><a href="install.html" >Installation</a></li><li id="xooki-cp_container" class="submenu"><a href="cp_container.html" >Classpath Container</a><ul class="closed"><li id="xooki-cpc/create"><a href="cpc/create.html" >Create a container</a></li><li id="xooki-cpc/edit"><a href="cpc/edit.html" >Edit the classpath</a></li><li id="xooki-cpc/resolve"><a href="cpc/resolve.html" >Launching resolve</a></li><li id="xooki-cpc/retrieve"><a href="cpc/retrieve.html" >Retrieve dependencies</a></li><li id="xooki-cpc/cleancache"><a href="cpc/cleancache.html" >Clean the caches</a></li><li id="xooki-cpc/reload_settings"><a href="cpc/reload_settings.html" >Reload settings</a></li><li id="xooki-cpc/workspace"><a href="cpc/work
space.html" >Resolve in workspace</a></li><li id="xooki-cpc/launch"><a href="cpc/launch.html" >Launch configuration</a></li><li id="xooki-cpc/maven"><a href="cpc/maven.html" >Use with maven poms</a></li><li id="xooki-cpc/wtp"><a href="cpc/wtp.html" >WTP integration</a></li></ul></li><li id="xooki-ivyeditor"><a href="ivyeditor.html" >Ivy file editor</a></li><li id="xooki-settingseditor"><a href="settingseditor.html" >Ivy settings editor</a></li><li id="xooki-preferences"><a href="preferences.html" >Eclipse global preferences</a></li><li id="xooki-eclipsevar"><a href="eclipsevar.html" >Eclipse variables</a></li><li id="xooki-console"><a href="console.html" >Ivy Console</a></li><li id="xooki-ant"><a href="ant.html" >Eclipse's Ant integration</a></li><li id="xooki-revdepexplorer"><a href="revdepexplorer.html" >Reverse Dependency Explorer</a></li><li id="xooki-dev" class="submenu"><a href="dev.html" >Developer doc</a><ul class="closed"><li id="xooki-dev/build"><a href="dev/build.
html" >Building</a></li><li id="xooki-dev/release"><a href="dev/release.html" >Releasing</a></li></ul></li></ul></li></ul></div>
+ <div class="content"><ul id="treemenu" class="treeview"><li id="xooki-index" class="submenu"><a href="index.html" >Documentation (trunk)</a><ul class="open"><li id="xooki-release-notes"><a href="release-notes.html" >Release Notes</a></li><li id="xooki-undefined"><a href="http://www.apache.org/licenses/" >License</a></li><li id="xooki-compatibility"><a href="compatibility.html" class="current">Compatibility</a></li><li id="xooki-install"><a href="install.html" >Installation</a></li><li id="xooki-cp_container" class="submenu"><a href="cp_container.html" >Classpath Container</a><ul class="closed"><li id="xooki-cpc/create"><a href="cpc/create.html" >Create a container</a></li><li id="xooki-cpc/edit"><a href="cpc/edit.html" >Edit the classpath</a></li><li id="xooki-cpc/resolve"><a href="cpc/resolve.html" >Launching resolve</a></li><li id="xooki-cpc/retrieve"><a href="cpc/retrieve.html" >Retrieve dependencies</a></li><li id="xooki-cpc/jarmapping"><a href="cpc/jarmapping.html" >J
ar mapping</a></li><li id="xooki-cpc/cleancache"><a href="cpc/cleancache.html" >Clean the caches</a></li><li id="xooki-cpc/reload_settings"><a href="cpc/reload_settings.html" >Reload settings</a></li><li id="xooki-cpc/workspace"><a href="cpc/workspace.html" >Resolve in workspace</a></li><li id="xooki-cpc/launch"><a href="cpc/launch.html" >Launch configuration</a></li><li id="xooki-cpc/maven"><a href="cpc/maven.html" >Use with maven poms</a></li><li id="xooki-cpc/wtp"><a href="cpc/wtp.html" >WTP integration</a></li></ul></li><li id="xooki-ivyeditor"><a href="ivyeditor.html" >Ivy file editor</a></li><li id="xooki-settingseditor"><a href="settingseditor.html" >Ivy settings editor</a></li><li id="xooki-preferences"><a href="preferences.html" >Eclipse global preferences</a></li><li id="xooki-eclipsevar"><a href="eclipsevar.html" >Eclipse variables</a></li><li id="xooki-console"><a href="console.html" >Ivy Console</a></li><li id="xooki-ant"><a href="ant.html" >Eclipse's Ant integr
ation</a></li><li id="xooki-revdepexplorer"><a href="revdepexplorer.html" >Reverse Dependency Explorer</a></li><li id="xooki-dev" class="submenu"><a href="dev.html" >Developer doc</a><ul class="closed"><li id="xooki-dev/build"><a href="dev/build.html" >Building</a></li><li id="xooki-dev/release"><a href="dev/release.html" >Releasing</a></li></ul></li></ul></li></ul></div>
</div>
@@ -81,13 +81,13 @@
<h1 class="title">Compatibility</h1>
<br class="xooki-br"/><h2>Upgrading/Downgrading</h2>
-This version is compatible with every earlier Apache release (since 2.0.0.alpha1). Any upgrade of IvyDE should work without any worries.<br class="xooki-br"/><br class="xooki-br"/>The reverse is not true, downgrading is not supported and may break your configuration<br class="xooki-br"/><br class="xooki-br"/><h2>Dependency on Ivy</h2>
+This version is compatible with every earlier Apache release (since 2.0.0.alpha1). Any upgrade of Apache IvyDE should work without any worries.<br class="xooki-br"/><br class="xooki-br"/>The reverse is not true, downgrading is not supported and may break your configuration<br class="xooki-br"/><br class="xooki-br"/><h2>Dependency on Apache Ivy</h2>
-IvyDE expects to be used with a version 2.1 or superior of Ivy.<br class="xooki-br"/><br class="xooki-br"/><h2>Eclipse integration</h2>
+Apache IvyDE expects to be used with a version 2.1 or superior of Apache Ivy.<br class="xooki-br"/><br class="xooki-br"/><h2>Eclipse™ integration</h2>
-IvyDE has been maintained to be compatible with Eclipse 3.2, 3.3, 3.4 and 3.5.<br class="xooki-br"/><br class="xooki-br"/><h2>JVM compability</h2>
+Apache IvyDE has been maintained to be compatible with Eclipse 3.4, 3.5 and 3.6.<br class="xooki-br"/><br class="xooki-br"/><h2>JVM compability</h2>
-IvyDE has been kept compatible with Java 1.4.<br class="xooki-br"/><br class="xooki-br"/>
+Apache IvyDE has been kept compatible with Java 1.4.<br class="xooki-br"/><br class="xooki-br"/>
<hr/>
<a href="?action=print">Printer Friendly</a>
</div><!-- main -->
@@ -111,7 +111,13 @@ IvyDE has been kept compatible with Java
-<div id="footer-message"></div>
+<div id="footer-message" class="footer">
+ <hr />
+ <i>Copyright © 2010 The Apache Software Foundation, Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0.txt">Apache License, Version 2.0</a>.</i><br />
+ <i>Apache IvyDE, Apache Ivy, Apache Ant, IvyDE, Ivy, Ant, Apache, the Apache IvyDE logo, the Apache Ivy logo, the Apache Ant logo and the Apache feather logo are trademarks of The Apache Software Foundation.</i><br />
+ <i>Eclipse and the Eclipse logo are trademarks of Eclipse Foundation, Inc.</i>
+ <i>All other marks mentioned may be trademarks or registered trademarks of their respective owners. </i>
+</div>
</div><!-- body -->