ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hi...@apache.org
Subject svn commit: r771082 - in /ant/ivy/ivyde/trunk/doc: ./ cpc/ images/
Date Sun, 03 May 2009 16:49:32 GMT
Author: hibou
Date: Sun May  3 16:49:31 2009
New Revision: 771082

URL: http://svn.apache.org/viewvc?rev=771082&view=rev
Log:
Lots of improvement of the doc to make it up to date

Added:
    ant/ivy/ivyde/trunk/doc/ant.html   (with props)
    ant/ivy/ivyde/trunk/doc/cpc/
    ant/ivy/ivyde/trunk/doc/cpc/cleancache.html   (with props)
    ant/ivy/ivyde/trunk/doc/cpc/create.html
      - copied, changed from r770960, ant/ivy/ivyde/trunk/doc/cp_container.html
    ant/ivy/ivyde/trunk/doc/cpc/edit.html
      - copied, changed from r770960, ant/ivy/ivyde/trunk/doc/cp_container.html
    ant/ivy/ivyde/trunk/doc/cpc/maven.html
      - copied, changed from r768394, ant/ivy/ivyde/trunk/doc/maven.html
    ant/ivy/ivyde/trunk/doc/cpc/reload_settings.html   (with props)
    ant/ivy/ivyde/trunk/doc/cpc/resolve.html
      - copied, changed from r770960, ant/ivy/ivyde/trunk/doc/cp_container.html
    ant/ivy/ivyde/trunk/doc/cpc/retrieve.html
      - copied, changed from r770960, ant/ivy/ivyde/trunk/doc/cp_container.html
    ant/ivy/ivyde/trunk/doc/cpc/workspace.html   (with props)
    ant/ivy/ivyde/trunk/doc/cpc/wtp.html   (with props)
    ant/ivy/ivyde/trunk/doc/images/addivylibrary.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/images/antedit.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/images/antpref.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/images/antrun.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/images/cleancache.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/images/pref_classpath.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/images/pref_retrieve.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/images/pref_settings.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/images/pref_workspace.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/images/reload_settings.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/images/resolveall.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/images/settings.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/images/settings_completion_att.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/images/settings_completion_struct.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/images/workspace.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/images/wtp.jpg   (with props)
    ant/ivy/ivyde/trunk/doc/ivyeditor.html
      - copied, changed from r768394, ant/ivy/ivyde/trunk/doc/editor.html
    ant/ivy/ivyde/trunk/doc/preferences.html
      - copied, changed from r768394, ant/ivy/ivyde/trunk/doc/index.html
    ant/ivy/ivyde/trunk/doc/settingseditor.html   (with props)
Removed:
    ant/ivy/ivyde/trunk/doc/editor.html
    ant/ivy/ivyde/trunk/doc/maven.html
Modified:
    ant/ivy/ivyde/trunk/doc/cp_container.html
    ant/ivy/ivyde/trunk/doc/dev.html
    ant/ivy/ivyde/trunk/doc/images/build_path_edit.jpg
    ant/ivy/ivyde/trunk/doc/images/pref.jpg
    ant/ivy/ivyde/trunk/doc/index.html
    ant/ivy/ivyde/trunk/doc/toc.json

Added: ant/ivy/ivyde/trunk/doc/ant.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/ant.html?rev=771082&view=auto
==============================================================================
--- ant/ivy/ivyde/trunk/doc/ant.html (added)
+++ ant/ivy/ivyde/trunk/doc/ant.html Sun May  3 16:49:31 2009
@@ -0,0 +1,57 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
+	<script type="text/javascript" src="xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Most Eclipse distribution includes a plugin to launch ant build files. The provided Ant is a standard distribution of Ant and so it doesn't include Ivy. But you probably want to use Ivy targets within the Eclipse's Ant.
+
+<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.
+
+In the global preference page of the Ant runtime, click on <b>Add External JARs...</b>
+
+<center><img src="images/antpref.jpg" /></center>
+
+Then browse your filesystem into the <tt>plugins</tt> directory of your Eclipse install, and select the Ivy jar named <tt>org.apache.ivy_2.X.X.XXXXXXXXX.jar</tt>. And that's it, Ivy has been added to the classpath of Ant embedded in Eclipse.
+
+<h1>Run Ivy targets</h1>
+
+Create an Ant build file and just declare the Ivy targets with:
+<code>
+    <taskdef resource="org/apache/ivy/ant/antlib.xml" uri="antlib:org.apache.ivy.ant" />
+</code>
+And don't forgot to declare the namespace <tt>xmlns:ivy="antlib:org.apache.ivy.ant"</tt>.
+
+Then you will be able to have completion on Ivy tasks:
+
+<center><img src="images/antedit.jpg" /></center>
+
+And run successul build:
+
+<center><img src="images/antrun.jpg" /></center>
+
+</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: ant/ivy/ivyde/trunk/doc/ant.html
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: ant/ivy/ivyde/trunk/doc/ant.html
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: ant/ivy/ivyde/trunk/doc/ant.html
------------------------------------------------------------------------------
    svn:mime-type = text/html

Modified: ant/ivy/ivyde/trunk/doc/cp_container.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cp_container.html?rev=771082&r1=771081&r2=771082&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cp_container.html (original)
+++ ant/ivy/ivyde/trunk/doc/cp_container.html Sun May  3 16:49:31 2009
@@ -24,58 +24,18 @@
 </head>
 <body>
 	<textarea id="xooki-source">
-You are fed up with updating the class path of all your projects each time you add or remove one dependency! <a href="index.html">IvyDE</a> will help you ! Better ... it will work for you!<br/>
-Indeed, <a href="index.html">IvyDE</a> can manage for you all your dependencies, based on a dependencies descriptor file (like ivy.xml file) it will provide a class path container for your IDE.<br/>
-<div style="padding:20px;">
-<table>
-<tr>
-<td><a href="maven.html"><img src="images/genial.jpg"></a></td>
-<td>&nbsp;&nbsp;&nbsp;</td>
-<td>Obviously IvyDE class path container can be based on a <b>ivy.xml</b> file, but it also manages <a href="maven.html">Maven pom.xml file!</a></td>
-</tr>
-</table>
-</div>
+As the Ivy's ant target to manage classpath, the IvyDE classpath container will help you manage the classpath of your Eclipse project, based on the dependencies declared in the Ivy files.
 
-<h1><a name="start"></a>Create the container</h1>
-
-You've just installed the IvyDE plugin from our <a href="../../download.html">updatesite</a>, and now you want to enjoy it quickly!<br/>
-Nothing easier, just follow these steps:
+So you probably want to:
 <ul>
-<li>Ensure the ivy.xml file or <a href="maven.html">maven pom.xml</a> can be accessed under the project folder of your eclipse "Navigator" view.<br/><br/></li>
-<li>Open the "Add Library" form of Eclipse (In package Explorer, in popup 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 "IvyDE Managed Dependencies" item.<br/><br/><center><img src="images/add_lib.jpg"/></center><br/><br/></li>
-<li>Select an ivy.xml file or a <a href="maven.html">maven pom.xml</a> and the desired configurations.<br/><br/><center><img src="images/ivy_file_def.jpg"/></center><br/><br/></li>
-<li><a name="localconf"></a>You then might want to have a special configuration for your project, a configuration different from the <a href="index.html#pref">global one</a>. For the ivy settings, click on the "Enable project specific settings" check box.<br/><br/><center><img src="images/project_specific_settings.jpg"/></center></li>
-<li><a name="retrieve"></a>On the next panel's tab, you can specify a retrieve job that will be launched on each resolve.<br/><br/><center><img src="images/retrieve.jpg"/></center></li>
-<li><a name="advanced"></a>You can also customize some advanced configuration of the classpath container: see the "Advanced" panel and click on "Enable project specific settings". Every configuration entry behaves exactly is the same way as the <a href="index.html#pref">global ones</a>.<br/><br/><center><img src="images/cp_advanced_conf.jpg"/></center></li>
-</ul><br/>
-Your class path is set and you can see all dependencies in one unique folder of the package explorer (folder name = &amp;amp;lt;ivy file name&amp;amp;gt;[&amp;amp;lt;configuration&amp;amp;gt;]).<br/><br/>
-<center> 
-<img src="images/cp_node.jpg">
-</center>
-
-<h1><a name="inlife"></a>Edit the container configuration</h1>
-
-<h2>Configure Ivy file and configuration</h2>
-During life of your project you can change the ivy.xml file or <a href="maven.html">maven pom.xml</a> and change the configuration you want
-to use.<br/>
-These properties can be accessed by contextual menu of the IvyDE class path container.
-<br/><br/>
-<center><img src="images/cp_configuration.jpg"></center>
-<br/>
-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 you will be able to click on the button "Edit": the IvyDE classpath container configuration dialog will pop up.
-This is particularly useful when Eclipse hides the empty classpath containers (since Eclipse 3.3), and then this is only way to trigger a resolve.
-<br/><br/>
-<center><img src="images/build_path_edit.jpg"></center>
-<br/>
-<h2>Resolve dependencies</h2>
-You can explicitly ask for a dependencies resolution from your class path container.
-
-This command will invoke the "resolve" ivy task and update your class path container.
-
-There is also a "refresh" action: this action is similar to the resolve one, it just doesn't do a full resolve if a report already exists in the cache. This is particularly useful if you work also with ant and a command line so you won't do two full resolve.
-<br/><br/>
-<center><img src="images/cp_resolve.jpg"></center><br/>
+    <li><a href="cpc/create.html">Create</a> a container</li>
+    <li><a href="cpc/edit.html">Edit</a> its setup</li>
+    <li>Launch the <a href="cpc/resolve.html">resolve</a> of the dependencies</li>
+    <li><a href="cpc/retrieve.html">Retrieve</a> the dependencies in your project</li>
+    <li>Resolve dependencies within the Eclipse <a href="cpc/workspace.html">workspace</a></li>
+    <li>Use IvyDE with <a href="cpc/maven.html">maven pom.xml</a></li>
+    <li>Use IvyDE in concert with <a href="cpc/wtp.html">WTP</a></li>
+</ul>
 </textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>

Added: ant/ivy/ivyde/trunk/doc/cpc/cleancache.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/cleancache.html?rev=771082&view=auto
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cpc/cleancache.html (added)
+++ ant/ivy/ivyde/trunk/doc/cpc/cleancache.html Sun May  3 16:49:31 2009
@@ -0,0 +1,42 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Within IvyDE it is possible to clean the different Ivy caches.
+
+On a configured IvyDE classpath container, open the contextual menu and select the <b>Clean Ivy cache</b> entry. It will then show the list of configured caches.
+
+<center><img src="../images/cleancache.jpg"/></center>
+
+<ul>
+    <li><u>All:</u> it will wipe out every cache</li>
+    <li><u>Resolution cache:</u> it will wipe out only the cache of resolution report</li>
+    <li><u>Every repository cache:</u> it will wipe out every cache dedicated to the artifacts</li>
+    <li><u>Cache 'xxxxxx':</u> it will wipe out only the cache with the specified name</li>
+</ul>
+</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: ant/ivy/ivyde/trunk/doc/cpc/cleancache.html
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: ant/ivy/ivyde/trunk/doc/cpc/cleancache.html
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: ant/ivy/ivyde/trunk/doc/cpc/cleancache.html
------------------------------------------------------------------------------
    svn:mime-type = text/html

Copied: ant/ivy/ivyde/trunk/doc/cpc/create.html (from r770960, ant/ivy/ivyde/trunk/doc/cp_container.html)
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/create.html?p2=ant/ivy/ivyde/trunk/doc/cpc/create.html&p1=ant/ivy/ivyde/trunk/doc/cp_container.html&r1=770960&r2=771082&rev=771082&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cp_container.html (original)
+++ ant/ivy/ivyde/trunk/doc/cpc/create.html Sun May  3 16:49:31 2009
@@ -19,63 +19,33 @@
 -->
 <html>
 <head>
-	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
-	<script type="text/javascript" src="xooki/xooki.js"></script>
+	<script type="text/javascript">var xookiConfig = {level: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
 </head>
 <body>
 	<textarea id="xooki-source">
-You are fed up with updating the class path of all your projects each time you add or remove one dependency! <a href="index.html">IvyDE</a> will help you ! Better ... it will work for you!<br/>
-Indeed, <a href="index.html">IvyDE</a> can manage for you all your dependencies, based on a dependencies descriptor file (like ivy.xml file) it will provide a class path container for your IDE.<br/>
-<div style="padding:20px;">
-<table>
-<tr>
-<td><a href="maven.html"><img src="images/genial.jpg"></a></td>
-<td>&nbsp;&nbsp;&nbsp;</td>
-<td>Obviously IvyDE class path container can be based on a <b>ivy.xml</b> file, but it also manages <a href="maven.html">Maven pom.xml file!</a></td>
-</tr>
-</table>
-</div>
+First you should have somewhere an ivy.xml file or a maven pom.xml ready to be used to build a classpath, along if needed with an ivysettings.xml.
 
-<h1><a name="start"></a>Create the container</h1>
-
-You've just installed the IvyDE plugin from our <a href="../../download.html">updatesite</a>, and now you want to enjoy it quickly!<br/>
-Nothing easier, just follow these steps:
+<h1>Standard creation</h1>
+The standard way to add the IvyDE classpath container is to manipulate the Eclipse's "Build Path":
 <ul>
-<li>Ensure the ivy.xml file or <a href="maven.html">maven pom.xml</a> can be accessed under the project folder of your eclipse "Navigator" view.<br/><br/></li>
-<li>Open the "Add Library" form of Eclipse (In package Explorer, in popup 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 "IvyDE Managed Dependencies" item.<br/><br/><center><img src="images/add_lib.jpg"/></center><br/><br/></li>
-<li>Select an ivy.xml file or a <a href="maven.html">maven pom.xml</a> and the desired configurations.<br/><br/><center><img src="images/ivy_file_def.jpg"/></center><br/><br/></li>
-<li><a name="localconf"></a>You then might want to have a special configuration for your project, a configuration different from the <a href="index.html#pref">global one</a>. For the ivy settings, click on the "Enable project specific settings" check box.<br/><br/><center><img src="images/project_specific_settings.jpg"/></center></li>
-<li><a name="retrieve"></a>On the next panel's tab, you can specify a retrieve job that will be launched on each resolve.<br/><br/><center><img src="images/retrieve.jpg"/></center></li>
-<li><a name="advanced"></a>You can also customize some advanced configuration of the classpath container: see the "Advanced" panel and click on "Enable project specific settings". Every configuration entry behaves exactly is the same way as the <a href="index.html#pref">global ones</a>.<br/><br/><center><img src="images/cp_advanced_conf.jpg"/></center></li>
-</ul><br/>
-Your class path is set and you can see all dependencies in one unique folder of the package explorer (folder name = &amp;amp;lt;ivy file name&amp;amp;gt;[&amp;amp;lt;configuration&amp;amp;gt;]).<br/><br/>
-<center> 
-<img src="images/cp_node.jpg">
-</center>
-
-<h1><a name="inlife"></a>Edit the container configuration</h1>
-
-<h2>Configure Ivy file and configuration</h2>
-During life of your project you can change the ivy.xml file or <a href="maven.html">maven pom.xml</a> and change the configuration you want
-to use.<br/>
-These properties can be accessed by contextual menu of the IvyDE class path container.
-<br/><br/>
-<center><img src="images/cp_configuration.jpg"></center>
-<br/>
-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 you will be able to click on the button "Edit": the IvyDE classpath container configuration dialog will pop up.
-This is particularly useful when Eclipse hides the empty classpath containers (since Eclipse 3.3), and then this is only way to trigger a resolve.
-<br/><br/>
-<center><img src="images/build_path_edit.jpg"></center>
-<br/>
-<h2>Resolve dependencies</h2>
-You can explicitly ask for a dependencies resolution from your class path container.
-
-This command will invoke the "resolve" ivy task and update your class path container.
-
-There is also a "refresh" action: this action is similar to the resolve one, it just doesn't do a full resolve if a report already exists in the cache. This is particularly useful if you work also with ant and a command line so you won't do two full resolve.
-<br/><br/>
-<center><img src="images/cp_resolve.jpg"></center><br/>
+<li>Select the project in which you want to create a IvyDE classpath container and open the "Add Libraries" form of Eclipse (In package Explorer, in popup 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 "IvyDE Managed Dependencies" item.<br/><br/><center><img src="../images/add_lib.jpg"/></center><br/><br/></li>
+<li>Select an ivy.xml file or a <a href="maven.html">maven pom.xml</a> and the desired configurations.<br/><br/><center><img src="../images/ivy_file_def.jpg"/></center><br/><br/></li>
+</ul>
+<li><a name="localconf"></a>You then might want to use specific settings for your project, a configuration different from the <a href="../preferences.html">global one</a>. For the ivy settings, click on the "Enable project specific settings" check box.<br/><br/><center><img src="../images/project_specific_settings.jpg"/></center></li>
+Your class path is set and you can see all dependencies in one unique folder of the package explorer (folder name = &amp;amp;lt;ivy file name&amp;amp;gt;[&amp;amp;lt;configuration&amp;amp;gt;]).
+
+
+<center><img src="../images/cp_node.jpg"></center>
+
+
+<h1>Fast creation</h1>
+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 will direclty access the prefilled setup of the IvyDE classpath container
+
+<center><img src="../images/addivylibrary.jpg"></center>
+
+
 </textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>

Copied: ant/ivy/ivyde/trunk/doc/cpc/edit.html (from r770960, ant/ivy/ivyde/trunk/doc/cp_container.html)
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/edit.html?p2=ant/ivy/ivyde/trunk/doc/cpc/edit.html&p1=ant/ivy/ivyde/trunk/doc/cp_container.html&r1=770960&r2=771082&rev=771082&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cp_container.html (original)
+++ ant/ivy/ivyde/trunk/doc/cpc/edit.html Sun May  3 16:49:31 2009
@@ -19,63 +19,24 @@
 -->
 <html>
 <head>
-	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
-	<script type="text/javascript" src="xooki/xooki.js"></script>
+	<script type="text/javascript">var xookiConfig = {level: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
 </head>
 <body>
 	<textarea id="xooki-source">
-You are fed up with updating the class path of all your projects each time you add or remove one dependency! <a href="index.html">IvyDE</a> will help you ! Better ... it will work for you!<br/>
-Indeed, <a href="index.html">IvyDE</a> can manage for you all your dependencies, based on a dependencies descriptor file (like ivy.xml file) it will provide a class path container for your IDE.<br/>
-<div style="padding:20px;">
-<table>
-<tr>
-<td><a href="maven.html"><img src="images/genial.jpg"></a></td>
-<td>&nbsp;&nbsp;&nbsp;</td>
-<td>Obviously IvyDE class path container can be based on a <b>ivy.xml</b> file, but it also manages <a href="maven.html">Maven pom.xml file!</a></td>
-</tr>
-</table>
-</div>
 
-<h1><a name="start"></a>Create the container</h1>
+During life of your project you can change the ivy.xml file or <a href="maven.html">maven pom.xml</a> and change the configuration you want
+to use.
 
-You've just installed the IvyDE plugin from our <a href="../../download.html">updatesite</a>, and now you want to enjoy it quickly!<br/>
-Nothing easier, just follow these steps:
-<ul>
-<li>Ensure the ivy.xml file or <a href="maven.html">maven pom.xml</a> can be accessed under the project folder of your eclipse "Navigator" view.<br/><br/></li>
-<li>Open the "Add Library" form of Eclipse (In package Explorer, in popup 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 "IvyDE Managed Dependencies" item.<br/><br/><center><img src="images/add_lib.jpg"/></center><br/><br/></li>
-<li>Select an ivy.xml file or a <a href="maven.html">maven pom.xml</a> and the desired configurations.<br/><br/><center><img src="images/ivy_file_def.jpg"/></center><br/><br/></li>
-<li><a name="localconf"></a>You then might want to have a special configuration for your project, a configuration different from the <a href="index.html#pref">global one</a>. For the ivy settings, click on the "Enable project specific settings" check box.<br/><br/><center><img src="images/project_specific_settings.jpg"/></center></li>
-<li><a name="retrieve"></a>On the next panel's tab, you can specify a retrieve job that will be launched on each resolve.<br/><br/><center><img src="images/retrieve.jpg"/></center></li>
-<li><a name="advanced"></a>You can also customize some advanced configuration of the classpath container: see the "Advanced" panel and click on "Enable project specific settings". Every configuration entry behaves exactly is the same way as the <a href="index.html#pref">global ones</a>.<br/><br/><center><img src="images/cp_advanced_conf.jpg"/></center></li>
-</ul><br/>
-Your class path is set and you can see all dependencies in one unique folder of the package explorer (folder name = &amp;amp;lt;ivy file name&amp;amp;gt;[&amp;amp;lt;configuration&amp;amp;gt;]).<br/><br/>
-<center> 
-<img src="images/cp_node.jpg">
-</center>
+These properties can be accessed by contextual menu of the IvyDE class path container:
 
-<h1><a name="inlife"></a>Edit the container configuration</h1>
+<center><img src="../images/cp_configuration.jpg"></center>
 
-<h2>Configure Ivy file and configuration</h2>
-During life of your project you can change the ivy.xml file or <a href="maven.html">maven pom.xml</a> and change the configuration you want
-to use.<br/>
-These properties can be accessed by contextual menu of the IvyDE class path container.
-<br/><br/>
-<center><img src="images/cp_configuration.jpg"></center>
-<br/>
 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 you will be able to click on the button "Edit": the IvyDE classpath container configuration dialog will pop up.
 This is particularly useful when Eclipse hides the empty classpath containers (since Eclipse 3.3), and then this is only way to trigger a resolve.
 <br/><br/>
-<center><img src="images/build_path_edit.jpg"></center>
+<center><img src="../images/build_path_edit.jpg"></center>
 <br/>
-<h2>Resolve dependencies</h2>
-You can explicitly ask for a dependencies resolution from your class path container.
-
-This command will invoke the "resolve" ivy task and update your class path container.
-
-There is also a "refresh" action: this action is similar to the resolve one, it just doesn't do a full resolve if a report already exists in the cache. This is particularly useful if you work also with ant and a command line so you won't do two full resolve.
-<br/><br/>
-<center><img src="images/cp_resolve.jpg"></center><br/>
 </textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>

Copied: ant/ivy/ivyde/trunk/doc/cpc/maven.html (from r768394, ant/ivy/ivyde/trunk/doc/maven.html)
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/maven.html?p2=ant/ivy/ivyde/trunk/doc/cpc/maven.html&p1=ant/ivy/ivyde/trunk/doc/maven.html&r1=768394&r2=771082&rev=771082&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/maven.html (original)
+++ ant/ivy/ivyde/trunk/doc/cpc/maven.html Sun May  3 16:49:31 2009
@@ -19,38 +19,57 @@
 -->
 <html>
 <head>
-	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
-	<script type="text/javascript" src="xooki/xooki.js"></script>
+	<script type="text/javascript">var xookiConfig = {level: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
 </head>
 <body>
 	<textarea id="xooki-source">
-<h1>General</h1>
-<p>If you want to use a maven pom.xml instead of ivy.xml file, you just have to select a pom file in the configuration form of IvyDE class path.<br/>When a maven pom is selected, the configurations list is updated with all maven scopes.</p>
-<p>Both examples below are a good illustration of maven pom use simplicity :</p>
+If you want to use a maven pom.xml instead of ivy.xml file, you just have to select a pom file in the configuration form of IvyDE class path.
+When a maven pom is selected, the configurations list is updated with all maven scopes.
+
+Both examples below are a good illustration of maven pom use simplicity :
 <ul>
 <li><a href="#one">Maven1 sample</a></li>
 <li><a href="#two">Maven2 sample</a></li>
 </ul>
 <h1><a name="one"></a>Maven1 Sample</h1>
-<p>This sample presents a simple use case of maven pom for IvyDE class path container. We are going to create an eclipse project on commons-httpclient sources.</p>
-<p><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></p>
-<p><b> - Unzip this file (c:/tmp/commons-httpclient/)</b></p>
-<p><b> - Create a new Eclipse java project based on the unzipped sources (c:/tmp/commons-httpclient/)</b><br />
-<center><img src="images/httpProject_errors.jpg"><br/><br />
-<u><b>Notes:</b></u> your project do not compile: some imports cannot be resolved.<br />
-</center><br />
-<b> - Add a new class path container based on the "project.xml" pom and select "default" configuration (maven scope)</b><br />
-<center><br />
-<img src="images/httpProject_pom.jpg"><br />
-</center><br />
-<b> - That's all : your project compiles !</b><br />
-<center><br />
-<img src="images/httpProject_clean.jpg"><br />
-</center></p>
+
+This sample presents a simple use case of maven pom for IvyDE class path container. We are going to create an eclipse project on commons-httpclient sources.
+
+<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>
+
+<b> - Unzip this file (c:/tmp/commons-httpclient/)</b>
+
+<b> - Create a new Eclipse java project based on the unzipped sources (c:/tmp/commons-httpclient/)</b>
+
+<center>
+<img src="../images/httpProject_errors.jpg"><br />
+<u><b>Notes:</b></u> your project do not compile: some imports cannot be resolved.
+
+</center>
+
+<b> - Add a new class path container based on the "project.xml" pom and select "default" configuration (maven scope)</b>
+
+<center>
+<img src="../images/httpProject_pom.jpg">
+</center>
+
+
+<b> - That's all : your project compiles !</b>
+
+<center>
+<img src="../images/httpProject_clean.jpg">
+</center>
+
+
 <h1><a name="two"></a>Maven2 Sample</h1>
-<p>This sample shows that IvyDE Class path container on a Maven2 pom can handle transitive dependancies.</p>
-<p><b> - Create a new empty java project in eclipse.</b></p>
-<p><b> - In your Ivy project configuration, set the ivy settings file below (Project/Properties/Ivy):</b></p>
+
+This sample shows that IvyDE Class path container on a Maven2 pom can handle transitive dependancies.
+
+<b> - Create a new empty java project in eclipse.</b>
+
+<b> - In your Ivy project configuration, set the ivy settings file below (Project/Properties/Ivy):</b>
+
 <code><ivysettings>
 	<conf defaultResolver="ibiblio"/>
 	<resolvers>
@@ -58,8 +77,13 @@
 	</resolvers>
 </ivysettings>
 </code>
-<p>Using the m2compatible attribute, you can benefit from Maven2 repository compatibility.<br/><br />
-<b> - Add the pom below in your project and select it for an IvyDE class path container choosing "compile" and "runtime" configurations.</b><br/></p>
+
+Using the m2compatible attribute, you can benefit from Maven2 repository compatibility.
+
+
+<b> - Add the pom below in your project and select it for an IvyDE class path container choosing "compile" and "runtime" configurations.</b>
+
+
 <code>
 <project>
 	<modelVersion>4.0.0</modelVersion>
@@ -76,9 +100,12 @@
 </project>
 </code>
 
-<p><b> - That's all ! Your IvyDE class path container gets all dependencies even those that were transitive to the commons-httpclient module !</b><br />
-<br/><br />
-<img src="images/maven2classpath.jpg"/></p>
+
+<b> - That's all ! Your IvyDE class path container gets all dependencies even those that were transitive to the commons-httpclient module !</b>
+
+<center>
+    <img src="../images/maven2classpath.jpg"/>
+</center>   
 </textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>

Added: ant/ivy/ivyde/trunk/doc/cpc/reload_settings.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/reload_settings.html?rev=771082&view=auto
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cpc/reload_settings.html (added)
+++ ant/ivy/ivyde/trunk/doc/cpc/reload_settings.html Sun May  3 16:49:31 2009
@@ -0,0 +1,40 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+In case you have selected the "Reload the settings only on demand" option in the <a href="../preferences.html#settings">preferences</a>, you can manually reload the settings via the context menu on the classpath container.
+
+<center><img src="../images/reload_settings.jpg"/></center>
+
+<u>Notes:</u>
+<ul>
+    <li>reloading the settings will automatically launch a resolve</li>
+    <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>
+
+</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: ant/ivy/ivyde/trunk/doc/cpc/reload_settings.html
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: ant/ivy/ivyde/trunk/doc/cpc/reload_settings.html
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: ant/ivy/ivyde/trunk/doc/cpc/reload_settings.html
------------------------------------------------------------------------------
    svn:mime-type = text/html

Copied: ant/ivy/ivyde/trunk/doc/cpc/resolve.html (from r770960, ant/ivy/ivyde/trunk/doc/cp_container.html)
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/resolve.html?p2=ant/ivy/ivyde/trunk/doc/cpc/resolve.html&p1=ant/ivy/ivyde/trunk/doc/cp_container.html&r1=770960&r2=771082&rev=771082&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cp_container.html (original)
+++ ant/ivy/ivyde/trunk/doc/cpc/resolve.html Sun May  3 16:49:31 2009
@@ -19,63 +19,23 @@
 -->
 <html>
 <head>
-	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
-	<script type="text/javascript" src="xooki/xooki.js"></script>
+	<script type="text/javascript">var xookiConfig = {level: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
 </head>
 <body>
 	<textarea id="xooki-source">
-You are fed up with updating the class path of all your projects each time you add or remove one dependency! <a href="index.html">IvyDE</a> will help you ! Better ... it will work for you!<br/>
-Indeed, <a href="index.html">IvyDE</a> can manage for you all your dependencies, based on a dependencies descriptor file (like ivy.xml file) it will provide a class path container for your IDE.<br/>
-<div style="padding:20px;">
-<table>
-<tr>
-<td><a href="maven.html"><img src="images/genial.jpg"></a></td>
-<td>&nbsp;&nbsp;&nbsp;</td>
-<td>Obviously IvyDE class path container can be based on a <b>ivy.xml</b> file, but it also manages <a href="maven.html">Maven pom.xml file!</a></td>
-</tr>
-</table>
-</div>
-
-<h1><a name="start"></a>Create the container</h1>
-
-You've just installed the IvyDE plugin from our <a href="../../download.html">updatesite</a>, and now you want to enjoy it quickly!<br/>
-Nothing easier, just follow these steps:
-<ul>
-<li>Ensure the ivy.xml file or <a href="maven.html">maven pom.xml</a> can be accessed under the project folder of your eclipse "Navigator" view.<br/><br/></li>
-<li>Open the "Add Library" form of Eclipse (In package Explorer, in popup 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 "IvyDE Managed Dependencies" item.<br/><br/><center><img src="images/add_lib.jpg"/></center><br/><br/></li>
-<li>Select an ivy.xml file or a <a href="maven.html">maven pom.xml</a> and the desired configurations.<br/><br/><center><img src="images/ivy_file_def.jpg"/></center><br/><br/></li>
-<li><a name="localconf"></a>You then might want to have a special configuration for your project, a configuration different from the <a href="index.html#pref">global one</a>. For the ivy settings, click on the "Enable project specific settings" check box.<br/><br/><center><img src="images/project_specific_settings.jpg"/></center></li>
-<li><a name="retrieve"></a>On the next panel's tab, you can specify a retrieve job that will be launched on each resolve.<br/><br/><center><img src="images/retrieve.jpg"/></center></li>
-<li><a name="advanced"></a>You can also customize some advanced configuration of the classpath container: see the "Advanced" panel and click on "Enable project specific settings". Every configuration entry behaves exactly is the same way as the <a href="index.html#pref">global ones</a>.<br/><br/><center><img src="images/cp_advanced_conf.jpg"/></center></li>
-</ul><br/>
-Your class path is set and you can see all dependencies in one unique folder of the package explorer (folder name = &amp;amp;lt;ivy file name&amp;amp;gt;[&amp;amp;lt;configuration&amp;amp;gt;]).<br/><br/>
-<center> 
-<img src="images/cp_node.jpg">
-</center>
-
-<h1><a name="inlife"></a>Edit the container configuration</h1>
-
-<h2>Configure Ivy file and configuration</h2>
-During life of your project you can change the ivy.xml file or <a href="maven.html">maven pom.xml</a> and change the configuration you want
-to use.<br/>
-These properties can be accessed by contextual menu of the IvyDE class path container.
-<br/><br/>
-<center><img src="images/cp_configuration.jpg"></center>
-<br/>
-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 you will be able to click on the button "Edit": the IvyDE classpath container configuration dialog will pop up.
-This is particularly useful when Eclipse hides the empty classpath containers (since Eclipse 3.3), and then this is only way to trigger a resolve.
-<br/><br/>
-<center><img src="images/build_path_edit.jpg"></center>
-<br/>
-<h2>Resolve dependencies</h2>
 You can explicitly ask for a dependencies resolution from your class path container.
 
 This command will invoke the "resolve" ivy task and update your class path container.
 
 There is also a "refresh" action: this action is similar to the resolve one, it just doesn't do a full resolve if a report already exists in the cache. This is particularly useful if you work also with ant and a command line so you won't do two full resolve.
-<br/><br/>
-<center><img src="images/cp_resolve.jpg"></center><br/>
+
+<center><img src="../images/cp_resolve.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.
+
+<center><img src="../images/resolveall.jpg"></center><br/>
+
 </textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>

Copied: ant/ivy/ivyde/trunk/doc/cpc/retrieve.html (from r770960, ant/ivy/ivyde/trunk/doc/cp_container.html)
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/retrieve.html?p2=ant/ivy/ivyde/trunk/doc/cpc/retrieve.html&p1=ant/ivy/ivyde/trunk/doc/cp_container.html&r1=770960&r2=771082&rev=771082&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cp_container.html (original)
+++ ant/ivy/ivyde/trunk/doc/cpc/retrieve.html Sun May  3 16:49:31 2009
@@ -19,63 +19,25 @@
 -->
 <html>
 <head>
-	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
-	<script type="text/javascript" src="xooki/xooki.js"></script>
+	<script type="text/javascript">var xookiConfig = {level: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
 </head>
 <body>
 	<textarea id="xooki-source">
-You are fed up with updating the class path of all your projects each time you add or remove one dependency! <a href="index.html">IvyDE</a> will help you ! Better ... it will work for you!<br/>
-Indeed, <a href="index.html">IvyDE</a> can manage for you all your dependencies, based on a dependencies descriptor file (like ivy.xml file) it will provide a class path container for your IDE.<br/>
-<div style="padding:20px;">
-<table>
-<tr>
-<td><a href="maven.html"><img src="images/genial.jpg"></a></td>
-<td>&nbsp;&nbsp;&nbsp;</td>
-<td>Obviously IvyDE class path container can be based on a <b>ivy.xml</b> file, but it also manages <a href="maven.html">Maven pom.xml file!</a></td>
-</tr>
-</table>
-</div>
-
-<h1><a name="start"></a>Create the container</h1>
-
-You've just installed the IvyDE plugin from our <a href="../../download.html">updatesite</a>, and now you want to enjoy it quickly!<br/>
-Nothing easier, just follow these steps:
-<ul>
-<li>Ensure the ivy.xml file or <a href="maven.html">maven pom.xml</a> can be accessed under the project folder of your eclipse "Navigator" view.<br/><br/></li>
-<li>Open the "Add Library" form of Eclipse (In package Explorer, in popup 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 "IvyDE Managed Dependencies" item.<br/><br/><center><img src="images/add_lib.jpg"/></center><br/><br/></li>
-<li>Select an ivy.xml file or a <a href="maven.html">maven pom.xml</a> and the desired configurations.<br/><br/><center><img src="images/ivy_file_def.jpg"/></center><br/><br/></li>
-<li><a name="localconf"></a>You then might want to have a special configuration for your project, a configuration different from the <a href="index.html#pref">global one</a>. For the ivy settings, click on the "Enable project specific settings" check box.<br/><br/><center><img src="images/project_specific_settings.jpg"/></center></li>
-<li><a name="retrieve"></a>On the next panel's tab, you can specify a retrieve job that will be launched on each resolve.<br/><br/><center><img src="images/retrieve.jpg"/></center></li>
-<li><a name="advanced"></a>You can also customize some advanced configuration of the classpath container: see the "Advanced" panel and click on "Enable project specific settings". Every configuration entry behaves exactly is the same way as the <a href="index.html#pref">global ones</a>.<br/><br/><center><img src="images/cp_advanced_conf.jpg"/></center></li>
-</ul><br/>
-Your class path is set and you can see all dependencies in one unique folder of the package explorer (folder name = &amp;amp;lt;ivy file name&amp;amp;gt;[&amp;amp;lt;configuration&amp;amp;gt;]).<br/><br/>
-<center> 
-<img src="images/cp_node.jpg">
-</center>
-
-<h1><a name="inlife"></a>Edit the container configuration</h1>
-
-<h2>Configure Ivy file and configuration</h2>
-During life of your project you can change the ivy.xml file or <a href="maven.html">maven pom.xml</a> and change the configuration you want
-to use.<br/>
-These properties can be accessed by contextual menu of the IvyDE class path container.
-<br/><br/>
-<center><img src="images/cp_configuration.jpg"></center>
-<br/>
-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 you will be able to click on the button "Edit": the IvyDE classpath container configuration dialog will pop up.
-This is particularly useful when Eclipse hides the empty classpath containers (since Eclipse 3.3), and then this is only way to trigger a resolve.
-<br/><br/>
-<center><img src="images/build_path_edit.jpg"></center>
-<br/>
-<h2>Resolve dependencies</h2>
-You can explicitly ask for a dependencies resolution from your class path container.
-
-This command will invoke the "resolve" ivy task and update your class path container.
-
-There is also a "refresh" action: this action is similar to the resolve one, it just doesn't do a full resolve if a report already exists in the cache. This is particularly useful if you work also with ant and a command line so you won't do two full resolve.
-<br/><br/>
-<center><img src="images/cp_resolve.jpg"></center><br/>
+It is possible to make IvyDE copy the resolved dependencies in your project: a retrieve of the dependencies can be triggered on each resolve of the classpath container.
+
+To enable it, enter the classpath container configuration panel, and hit the second tab "Retrieve".
+
+<center><img src="../images/retrieve.jpg"/></center>
+
+So you can choose to <b>do retrieve after resolve</b> the dependencies.
+
+The <b>Retrieve pattern</b> specified the location where the deendencies should be copied, location raltive to the containing project.
+
+The <b>Delete old retrieved artifacts</b> check box will enable the wipe out the output directory before each retrieve.
+
+And finally you can select in which <b>Configurations</b> the dependencies should be resolved and you can select which <b>Types</b> of artifact should be actually retrieved. In both fields, <i>*</i> will means <i>all</i>.
+
 </textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>

Added: ant/ivy/ivyde/trunk/doc/cpc/workspace.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/workspace.html?rev=771082&view=auto
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cpc/workspace.html (added)
+++ ant/ivy/ivyde/trunk/doc/cpc/workspace.html Sun May  3 16:49:31 2009
@@ -0,0 +1,46 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Some projects are composed of mulpliple modules, modules having dependencies between them, dependencies managed by Ivy (of course!). Then sometimes we need to build and publish some modules before building the dependant one. Eclipse can handle classpath composed of Java project, it can handles dependencies between projects, and IvyDE can use that feature.
+
+First every of your modules should be separated projects in Eclipse, and each of this project should have an IvyDE classpath container configured.
+
+To enable resolution in the workspace, go into the advanced configuration panel of the classpath container and select <b>Resolve dependencies in workspace</b>.
+
+<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>
+    <li>obviously the <i>org</i> and <i>name</i> </li>
+    <li>if there is a <i>rev</i> specified, dependencies should specify the appropriate range</li>
+    <li>if there is no <i>rev</i> specified, only dependencies with <i>lastest</i> will match</li>
+    <li>the <i>status</i> should match the required one: a dependency with <i>latest.integration</i> will only match if there is <i>status="interation"</i> in the info of the dependant module</li>
+</ul>
+
+</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: ant/ivy/ivyde/trunk/doc/cpc/workspace.html
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: ant/ivy/ivyde/trunk/doc/cpc/workspace.html
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: ant/ivy/ivyde/trunk/doc/cpc/workspace.html
------------------------------------------------------------------------------
    svn:mime-type = text/html

Added: ant/ivy/ivyde/trunk/doc/cpc/wtp.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/wtp.html?rev=771082&view=auto
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cpc/wtp.html (added)
+++ ant/ivy/ivyde/trunk/doc/cpc/wtp.html Sun May  3 16:49:31 2009
@@ -0,0 +1,38 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+WTP is the <a href="http://www.eclipse.org/webtools/">Web Tools Platform</a> project from the Eclipse fondation which allow to easily develop, launch and debug web applications. IvyDE can be used with this framework, but only from the version 2.0 of WTP, which is supported since Eclipse 3.3.
+
+In the properties of your project configured to use WTP, there is a section "Java EE Module Dependencies". There should be your configured IvyDE classpath container listed, usually with the name "ivy.xml [*]". Just select it and the Ivy dependencies will be deployed as well.
+
+<center><img src="../images/wtp.jpg"/></center>
+
+This has been successfully tested with Eclipse 3.3 and WTP 2.0, Eclipse 3.4 and WTP 3.0.
+
+</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: ant/ivy/ivyde/trunk/doc/cpc/wtp.html
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: ant/ivy/ivyde/trunk/doc/cpc/wtp.html
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: ant/ivy/ivyde/trunk/doc/cpc/wtp.html
------------------------------------------------------------------------------
    svn:mime-type = text/html

Modified: ant/ivy/ivyde/trunk/doc/dev.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/dev.html?rev=771082&r1=771081&r2=771082&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/dev.html (original)
+++ ant/ivy/ivyde/trunk/doc/dev.html Sun May  3 16:49:31 2009
@@ -26,7 +26,12 @@
 <body>
 	<textarea id="xooki-source">
 Adding features or fixing bugs needs a little more involvement.
-You will find here the basics to get into it.</textarea>
+You will find here the basics to get into it:
+<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>
+</ul>
+</textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>
 </html>

Added: ant/ivy/ivyde/trunk/doc/images/addivylibrary.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/addivylibrary.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/addivylibrary.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: ant/ivy/ivyde/trunk/doc/images/antedit.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/antedit.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/antedit.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: ant/ivy/ivyde/trunk/doc/images/antpref.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/antpref.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/antpref.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: ant/ivy/ivyde/trunk/doc/images/antrun.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/antrun.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/antrun.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Modified: ant/ivy/ivyde/trunk/doc/images/build_path_edit.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/build_path_edit.jpg?rev=771082&r1=771081&r2=771082&view=diff
==============================================================================
Binary files - no diff available.

Added: ant/ivy/ivyde/trunk/doc/images/cleancache.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/cleancache.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/cleancache.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Modified: ant/ivy/ivyde/trunk/doc/images/pref.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/pref.jpg?rev=771082&r1=771081&r2=771082&view=diff
==============================================================================
Binary files - no diff available.

Added: ant/ivy/ivyde/trunk/doc/images/pref_classpath.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/pref_classpath.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/pref_classpath.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: ant/ivy/ivyde/trunk/doc/images/pref_retrieve.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/pref_retrieve.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/pref_retrieve.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: ant/ivy/ivyde/trunk/doc/images/pref_settings.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/pref_settings.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/pref_settings.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: ant/ivy/ivyde/trunk/doc/images/pref_workspace.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/pref_workspace.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/pref_workspace.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: ant/ivy/ivyde/trunk/doc/images/reload_settings.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/reload_settings.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/reload_settings.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: ant/ivy/ivyde/trunk/doc/images/resolveall.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/resolveall.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/resolveall.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: ant/ivy/ivyde/trunk/doc/images/settings.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/settings.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/settings.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: ant/ivy/ivyde/trunk/doc/images/settings_completion_att.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/settings_completion_att.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/settings_completion_att.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: ant/ivy/ivyde/trunk/doc/images/settings_completion_struct.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/settings_completion_struct.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/settings_completion_struct.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: ant/ivy/ivyde/trunk/doc/images/workspace.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/workspace.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/workspace.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: ant/ivy/ivyde/trunk/doc/images/wtp.jpg
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/images/wtp.jpg?rev=771082&view=auto
==============================================================================
Binary file - no diff available.

Propchange: ant/ivy/ivyde/trunk/doc/images/wtp.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Modified: ant/ivy/ivyde/trunk/doc/index.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/index.html?rev=771082&r1=771081&r2=771082&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/index.html (original)
+++ ant/ivy/ivyde/trunk/doc/index.html Sun May  3 16:49:31 2009
@@ -24,51 +24,15 @@
 </head>
 <body>
 	<textarea id="xooki-source">
-IvyDE can be considered as the merge of two tools:
+IvyDE is the Eclipse plugin which intergrate Ivy into your java development enviromnent. It includes:
 <ul>
-<li><a href="editor.html">Ivy xml files Editor</a>: creation wizard, html preview and completion for Ivy xml tag, attributes but also attributes' values.</li>
-<li><a href="cp_container.html">Class path container</a>: Automatic downloads, access "resolve" task from your IDE</li>
+<li><a href="ivyeditor.html">an Ivy xml files editor</a>: creation wizard, html preview and completion for Ivy xml tag, attributes but also attributes' values.</li>
+<li><a href="settingseditor.html">an Ivy settings files editor</a>: completion for xml tag, attributes but also attributes' values.</li>
+<li><a href="cp_container.html">a classpath container</a>: automatic downloads, access "resolve" task from your IDE, and <a href="cpc/workspace.html">resolve in Eclipse's workspace</a></li>
+<li><a href="cp_container.html">an Ivy console</a>: presents every log from Ivy, really helpful to debug a failing resolve</li>
 </ul>
 
-Then you are probably interested by the [[console Ivy console]] which contains every log from Ivy. So it is really helpful when trying to find why a resolve failed.
-
-<h1><a name="install"></a>Plugin installation</h1>
-
-Before trying to use it, let's install it!
-
-The trunk version has not been release yet, so you should install it by [[build building it yourself]].
-
-<h1><a name="pref"></a>Eclipse Preference Page</h1>
-
-There is a global configuration page, which control the behaviour of every Ivy instance in every project. You can also configure it <a href="cp_container.html#localconf">by project</a>.
-
-The global configuration can be found in the global configuration panel of Eclipse (menu Window>Preferences for Windows and Linux users, Eclipse>Preferences for mac users), and select the item Ivy.
-
-<img src="images/pref.jpg"/><br/>
-<ul><b>Global settings:</b>
-	<li><u>Ivy settings URL:</u> specify here the path to your ivy settings file. Leave it blank to use Ivy default resolvers</li>
-</ul>
-<ul><b>Retrieve configuration:</b><br/>
-    If checked, some retrieve job will be triggered after each the resolve.<br/>
-	<li><u>Retrieve pattern:</u> the pattern to use for the retrieve. Check <a href="../../../history/latest-milestone/use/retrieve.html">Ivy documentation</a> for pattern explanation.</li>
-        <li><u>Delete old retrieve artifacts:</u> on each retrieve, the previously retrieved libraries will be removed (similar to the sync argument in the ant task)</li>
-        <li><u>Retrieve configurations:</u> the configurations to retrieve (a comma separated list)</li>
-        <li><u>Retrieve types:</u> the types of artifact to retrieve (a comma separated list)</li>
-</ul>
-<ul><b>Classpath container configuration:</b>
-	<li><u>Project dependencies:</u> IvyDE can try to make dependencies between project more than to jars into a repository.
-	    <u><i>Important note:</i></u> this feature is quite limited for now, it just tries to replace jar dependencies with project dependencies, based on the module id of the jar, and the projects configured to use IvyDE; the version is not taken into consideration, and even if a project match a dependency, the jar of the dependency have to be resolved from a repository.</li>
-	<li><u>Order alphabetically:</u> by default in the classpath container the entries are ordered by order of declaration. When there are many entries, it could be useful to have them ordered alphabetically so that you can find them faster.</li>
-	<li><u>Accepted types:</u> a comma separated list of extensions which will make IvyDE add the artifact to the classpath</li>
-	<li><u>Sources types:</u> a comma separated list of ivy "type" which will make IvyDE consider them as sources</li>
-	<li><u>Sources suffixes:</u> a comma separated list of suffixes which will make IvyDE attach as source the artifact with the suffix to the artifact without the suffix. For instance, "commons-lang-sources.jar" will be attached as source to "commons-lang.jar" with the default value.</li>
-	<li><u>Javadoc types:</u> same as sources types but for javadocs</li>
-	<li><u>Javadoc suffixes:</u> same as sources suffixes but for javadocs</li>
-</ul>
-<ul><b>Editor information:</b>
-	<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>
-</ul>
+And IvyDE can be also used with other plugins like <a href="cpc/wtp.html">WTP</a> or <a href="ant.html">Ant</a>.
 
 </textarea>
 <script type="text/javascript">xooki.postProcess();</script>

Copied: ant/ivy/ivyde/trunk/doc/ivyeditor.html (from r768394, ant/ivy/ivyde/trunk/doc/editor.html)
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/ivyeditor.html?p2=ant/ivy/ivyde/trunk/doc/ivyeditor.html&p1=ant/ivy/ivyde/trunk/doc/editor.html&r1=768394&r2=771082&rev=771082&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/editor.html (original)
+++ ant/ivy/ivyde/trunk/doc/ivyeditor.html Sun May  3 16:49:31 2009
@@ -24,40 +24,55 @@
 </head>
 <body>
 	<textarea id="xooki-source">
-Edit your ivy files easily in eclipse with the <a href="index.html">IvyDE</a> Plugin editor.<br/> <a href="index.html">IvyDE</a> brings creation wizard, html preview and completion for Ivy xml tag, attributes but also for attributes' values!<br/>
-Choose an organisation and browse thru its projects and revisions.<br/>
+Edit your ivy files easily in eclipse with the <a href="index.html">IvyDE</a> Plugin editor.
+<a href="index.html">IvyDE</a> brings creation wizard, html preview and completion for Ivy xml tag, attributes but also for attributes' values!
+Choose an organisation and browse thru its projects and revisions.
 
-<h1>Content</h1>
-<ul>
-<li><a href="#wizard">Wizard</a></li>
-<li><a href="#editor">Editor</a></li>
-</ul>
+<h1><a name="wizard"></a>Wizard</h1>
+
+IvyDE comes with a wizard that allows you to create an ivy.xml file for your project.
+To open the wizard choose File->New->Other in the Eclipse menu (Ctrl+N by default)
+The Ivy wizard is accessible in the category Other. Select it then click Next
+
+<center><img src="images/wizard1.jpg"/></center>
+
+
+The wizard contains only one page, and is very simple.
+
+<center><img src="images/wizard2.jpg"/></center>
 
 
-<h1><a name="wizard"></a>Wizard</h1>
-IvyDE comes with a wizard that allows you to create an ivy.xml file for your project.<br/>
-To open the wizard choose File->New->Other in the Eclipse menu (Ctrl+N by default)<br/>
-The Ivy wizard is accessible in the category Other. Select it then click Next<br/><br/>
-<img src="images/wizard1.jpg"/><br/><br/>
-The wizard contains only one page, and is very simple.<br/><br/>
-<img src="images/wizard2.jpg"/><br/>
 <ol><b>Wizard fields:</b>
 	<li> Container: you have to select the targeted project. (This is already set if you access the wizard thanks right click menu on your project root folder)</li>
 	<li> File name: the ivy file name. (ivy.xml by default and its better to keep it in most of case)</li>
-	<li> Organisation: the component owner name. (your company name or the company that provides the component if you are writing ivy.xml file for 3rd party jars). Note this value can be set in the <a href="index.html#pref">Ivy preference page</a></li>
+	<li> Organisation: the component owner name. (your company name or the company that provides the component if you are writing ivy.xml file for 3rd party jars). Note this value can be set in the <a href="preferences.html">Ivy preference page</a></li>
 	<li> Module name: the component name.</li>
 	<li> Status: the status of the project. (integration by default since we have just created its ivy file :-). Please refer to <a href="../../../history/latest-milestone/index.html">Ivy documentation for more details</a>)</li>
 </ol>
-When the form is correctly filled you can press Finish button. Eclipse will automatically open the Ivy <a href="#editor">editor</a>.<br/>
+When the form is correctly filled you can press Finish button. Eclipse will automatically open the Ivy <a href="#editor">editor</a>.
+
 
 <h1><a name="editor"></a>Ivy Editor</h1>
 
-<img src="images/editor1.jpg"/><br/><br/>
-The Ivy's eclipse editor provides xml syntax coloration, tag completion, tag's attribute names completion, and for dependency and configuration tag value completion.<br/>
-Completion comes with contextual help. The completion popup is displayed when hitting simultaneously the CTRL and the SPACE keys.<br/><br/>
+<center><img src="images/editor1.jpg"/></center>
+
+
+The Ivy's eclipse editor provides xml syntax coloration, tag completion, tag's attribute names completion, and for dependency and configuration tag value completion.
+
+Completion comes with contextual help. The completion popup is displayed when hitting simultaneously the CTRL and the SPACE keys.
+
+
 <b>Available completions:</b><ul>
-	<li><b>Xml structure</b>: allows you quickly to insert the good tag at its right place. If the tag can have nested children both notations, simple tag and open tag, are proposed<br/><br/><img src="images/completion1.jpg"/></li>
-	<li><b>Tag attributes</b>: when your cursor is placed in a tag bracket the completion show available attributes for the enclosing tag.<br/><br/><img src="images/completion2.jpg"/></li>
+	<li><b>Xml structure</b>: allows you quickly to insert the good tag at its right place. If the tag can have nested children both notations, simple tag and open tag, are proposed
+	    
+	    <center><img src="images/completion1.jpg"/></center>
+	    
+	</li>
+	<li><b>Tag attributes</b>: when your cursor is placed in a tag bracket the completion show available attributes for the enclosing tag.
+	    
+	    <center><img src="images/completion2.jpg"/></center>
+	    
+	</li>
 	<li><b>Attributes values</b>: when your cursor is placed in the quote of an attribute value the completion shows available values for the matching attribute.
 		<br/>
 		<ul>Available value completion
@@ -68,8 +83,11 @@
 			<li> <i>info/repository: </i> name (the other attributes depend on it), url, ivys, pattern, artifacts</li>
 			<li> <i>configurations/conf: </i> visibility,  deprecated, extends </li>
 			<li> <i>publications/artifact: </i>type, conf, ext</li>
-			<li> <i>dependencies/dependency: </i>org, name, rev are resolved thanks to Ivy using the ivyconf set in the <a href="index.html#project_pref">project Ivy preference page</a>. If not set to "default" Ivy uses its defaults resolvers configuration (ie ivyrep + ibiblio), and if not set Ivy uses the ivyconf set in the <a href="index.html#pref">Eclipse Ivy preference page</a>. conf values are computed from current ivy.xml file and the dependency ivy.xml file if any.<br/>
-					<br/><img src="images/completion4.jpg"/></li>
+			<li> <i>dependencies/dependency: </i>org, name, rev are resolved thanks to Ivy using the ivyconf set in the <a href="cpc/edit.html">project Ivy preference page</a>. If not set to "default" Ivy uses its defaults resolvers configuration (ie ivyrep + ibiblio), and if not set Ivy uses the ivyconf set in the <a href="preferences.html">Eclipse Ivy preference page</a>. conf values are computed from current ivy.xml file and the dependency ivy.xml file if any.
+			    
+			    <center><img src="images/completion4.jpg"/></center>
+			
+			</li>
 		</ul>
 	</li>
 </ul>

Copied: ant/ivy/ivyde/trunk/doc/preferences.html (from r768394, ant/ivy/ivyde/trunk/doc/index.html)
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/preferences.html?p2=ant/ivy/ivyde/trunk/doc/preferences.html&p1=ant/ivy/ivyde/trunk/doc/index.html&r1=768394&r2=771082&rev=771082&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/index.html (original)
+++ ant/ivy/ivyde/trunk/doc/preferences.html Sun May  3 16:49:31 2009
@@ -24,52 +24,66 @@
 </head>
 <body>
 	<textarea id="xooki-source">
-IvyDE can be considered as the merge of two tools:
-<ul>
-<li><a href="editor.html">Ivy xml files Editor</a>: creation wizard, html preview and completion for Ivy xml tag, attributes but also attributes' values.</li>
-<li><a href="cp_container.html">Class path container</a>: Automatic downloads, access "resolve" task from your IDE</li>
-</ul>
-
-Then you are probably interested by the [[console Ivy console]] which contains every log from Ivy. So it is really helpful when trying to find why a resolve failed.
+IvyDE maintain a global configuration, which control the behaviour of every Ivy instance in every project in the workspace. Though this global configuration can be overided in each <a href="cpc/edit.html">project</a>.
 
-<h1><a name="install"></a>Plugin installation</h1>
+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.
 
-Before trying to use it, let's install it!
+<h1><a name="global"></a>Global Ivy preferences</h1>
 
-The trunk version has not been release yet, so you should install it by [[build building it yourself]].
+<center><img src="images/pref.jpg"/></center>
 
-<h1><a name="pref"></a>Eclipse Preference Page</h1>
+<ul>
+	<li><u>On Eclipse startup:</u> it specifies what IvyDE should do in every project when Eclipse is starting up</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>
+</ul>
 
-There is a global configuration page, which control the behaviour of every Ivy instance in every project. You can also configure it <a href="cp_container.html#localconf">by project</a>.
+<h1><a name="classpath"></a>Classpath configuration</h1>
 
-The global configuration can be found in the global configuration panel of Eclipse (menu Window>Preferences for Windows and Linux users, Eclipse>Preferences for mac users), and select the item Ivy.
+<center><img src="images/pref_classpath.jpg"/></center>
 
-<img src="images/pref.jpg"/><br/>
-<ul><b>Global settings:</b>
-	<li><u>Ivy settings URL:</u> specify here the path to your ivy settings file. Leave it blank to use Ivy default resolvers</li>
+<ul>
+	<li><u>Resolve dependencies in workpace:</u> IvyDE can try to make dependencies between project more than to jars into a repository. See the <a href="cpc/workspace.html">documentation</a> for further info.</li>
+	<li><u>Order of the classpath entries:</u> by default in the classpath container the entries are ordered by order of declaration in the ivy.xml. When there are many entries, it could be useful to have them ordered alphabetically so that you can find them faster.</li>
+	<li><u>Accepted types:</u> a comma separated list of extensions which will make IvyDE add the artifact to the classpath</li>
+	<li><u>Sources types:</u> a comma separated list of Ivy "type" which will make IvyDE consider them as sources</li>
+	<li><u>Sources suffixes:</u> a comma separated list of suffixes which will make IvyDE attach as source the artifact with the suffix to the artifact without the suffix. For instance, "commons-lang-sources.jar" will be attached as source to "commons-lang.jar" with the default value.</li>
+	<li><u>Javadoc types:</u> same as sources types but for javadocs</li>
+	<li><u>Javadoc suffixes:</u> same as sources suffixes but for javadocs</li>
 </ul>
-<ul><b>Retrieve configuration:</b><br/>
+
+<h1><a name="retrieve"></a>Retrieve setup</h1>
+
+<center><img src="images/pref_retrieve.jpg"/></center>
+
+<ul>
     If checked, some retrieve job will be triggered after each the resolve.<br/>
 	<li><u>Retrieve pattern:</u> the pattern to use for the retrieve. Check <a href="../../../history/latest-milestone/use/retrieve.html">Ivy documentation</a> for pattern explanation.</li>
         <li><u>Delete old retrieve artifacts:</u> on each retrieve, the previously retrieved libraries will be removed (similar to the sync argument in the ant task)</li>
         <li><u>Retrieve configurations:</u> the configurations to retrieve (a comma separated list)</li>
         <li><u>Retrieve types:</u> the types of artifact to retrieve (a comma separated list)</li>
 </ul>
-<ul><b>Classpath container configuration:</b>
-	<li><u>Project dependencies:</u> IvyDE can try to make dependencies between project more than to jars into a repository.
-	    <u><i>Important note:</i></u> this feature is quite limited for now, it just tries to replace jar dependencies with project dependencies, based on the module id of the jar, and the projects configured to use IvyDE; the version is not taken into consideration, and even if a project match a dependency, the jar of the dependency have to be resolved from a repository.</li>
-	<li><u>Order alphabetically:</u> by default in the classpath container the entries are ordered by order of declaration. When there are many entries, it could be useful to have them ordered alphabetically so that you can find them faster.</li>
-	<li><u>Accepted types:</u> a comma separated list of extensions which will make IvyDE add the artifact to the classpath</li>
-	<li><u>Sources types:</u> a comma separated list of ivy "type" which will make IvyDE consider them as sources</li>
-	<li><u>Sources suffixes:</u> a comma separated list of suffixes which will make IvyDE attach as source the artifact with the suffix to the artifact without the suffix. For instance, "commons-lang-sources.jar" will be attached as source to "commons-lang.jar" with the default value.</li>
-	<li><u>Javadoc types:</u> same as sources types but for javadocs</li>
-	<li><u>Javadoc suffixes:</u> same as sources suffixes but for javadocs</li>
+
+<h1><a name="settings"></a>Ivy settings</h1>
+
+<center><img src="images/pref_settings.jpg"/></center>
+
+<ul>
+	<li><u>Ivy settings URL:</u> specify here the path to your ivy settings file. Leave it blank to use Ivy default resolvers</li>
+	<li><u>Reload the settings only on demand:</u> by default IvyDE will parse the ivysettings each times it needs it (each resolve, refresh, clean cache or completion in the ivy editor). For remote ivysettings this can slow down dramatically the UI, so it is possible to make IvyDE keep the settings in cache and only reload it via the context menu on the container)</li>
+	<li><u>Property files:</u> this is a comma separated ist if java properties files which are loaded along with the settings.</li>
 </ul>
-<ul><b>Editor information:</b>
-	<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>
+
+<h1><a name="workspace"></a>Workspace resolver</h1>
+
+<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>
+	<li><u>opening trigger resolve:</u> when a project is opened IvyDE will trigger the resolve of every other project which has the workspace resolver enabled</li>
 </ul>
 
+
 </textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>

Added: ant/ivy/ivyde/trunk/doc/settingseditor.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/settingseditor.html?rev=771082&view=auto
==============================================================================
--- ant/ivy/ivyde/trunk/doc/settingseditor.html (added)
+++ ant/ivy/ivyde/trunk/doc/settingseditor.html Sun May  3 16:49:31 2009
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
+	<script type="text/javascript" src="xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+IvyDE provides an editor of ivysettings.xml files which make the edition of such files simple. It provides completion on every tags and attribute names.
+
+<center><img src="images/settings.jpg"/></center>
+
+Completion comes with contextual help. The completion popup is displayed when hitting simultaneously the CTRL and the SPACE keys.
+
+<b>Available completions:</b><ul>
+	<li><b>Xml structure</b>: allows you quickly to insert the good tag at its right place. If the tag can have nested children both notations, simple tag and open tag, are proposed
+	    
+	    <center><img src="images/settings_completion_struct.jpg"/></center>
+	    
+	</li>
+	<li><b>Tag attributes</b>: when your cursor is placed in a tag bracket the completion show available attributes for the enclosing tag.
+	    
+	    <center><img src="images/settings_completion_att.jpg"/></center>
+
+	</li>
+</ul>
+
+</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: ant/ivy/ivyde/trunk/doc/settingseditor.html
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: ant/ivy/ivyde/trunk/doc/settingseditor.html
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: ant/ivy/ivyde/trunk/doc/settingseditor.html
------------------------------------------------------------------------------
    svn:mime-type = text/html

Modified: ant/ivy/ivyde/trunk/doc/toc.json
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/toc.json?rev=771082&r1=771081&r2=771082&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/toc.json (original)
+++ ant/ivy/ivyde/trunk/doc/toc.json Sun May  3 16:49:31 2009
@@ -5,22 +5,91 @@
         "title":"Documentation",
         "children": [
             {
-              "id":"editor",
-              "title":"Editor",
+              "id":"cp_container",
+              "title":"Classpath Container",
               "children": [
+                  {
+                    "id":"cpc/create",
+                    "title":"Create a container",
+                    "children": [
 
+                    ]
+                  },
+                  {
+                    "id":"cpc/edit",
+                    "title":"Edit the classpath",
+                    "children": [
+
+                    ]
+                  },
+                  {
+                    "id":"cpc/resolve",
+                    "title":"Launching resolve",
+                    "children": [
+
+                    ]
+                  },
+                  {
+                    "id":"cpc/retrieve",
+                    "title":"Retrieve the dependencies",
+                    "children": [
+
+                    ]
+                  },
+                  {
+                    "id":"cpc/cleancache",
+                    "title":"Clean the caches",
+                    "children": [
+
+                    ]
+                  },
+                  {
+                    "id":"cpc/reload_settings",
+                    "title":"Reload settings",
+                    "children": [
+
+                    ]
+                  },
+                  {
+                    "id":"cpc/workspace",
+                    "title":"Resolve in workspace",
+                    "children": [
+
+                    ]
+                  },
+                  {
+                    "id":"cpc/maven",
+                    "title":"Use with maven poms",
+                    "children": [
+
+                    ]
+                  },
+                  {
+                    "id":"cpc/wtp",
+                    "title":"WTP integration",
+                    "children": [
+
+                    ]
+                  },
                 ]
             },
             {
-              "id":"cp_container",
-              "title":"Classpath Container",
+              "id":"ivyeditor",
+              "title":"Ivy file editor",
+              "children": [
+
+                ]
+            },
+            {
+              "id":"settingseditor",
+              "title":"Ivy settings editor",
               "children": [
 
                 ]
             },
             {
-              "id":"maven",
-              "title":"Use with maven poms",
+              "id":"preferences",
+              "title":"Eclipse global preferences",
               "children": [
 
                 ]
@@ -33,6 +102,13 @@
                 ]
             },
             {
+              "id":"ant",
+              "title":"Eclipse's Ant interation",
+              "children": [
+
+                ]
+            },
+            {
               "id":"dev",
               "title":"Developer doc",
               "children": [



Mime
View raw message