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 2008/09/28 16:04:49 UTC
svn commit: r699819 - /ant/ivy/site/target/ivyde/faq.html
Author: hibou
Date: Sun Sep 28 07:04:49 2008
New Revision: 699819
URL: http://svn.apache.org/viewvc?rev=699819&view=rev
Log:
regeneration of the IvyDE website
Modified:
ant/ivy/site/target/ivyde/faq.html
Modified: ant/ivy/site/target/ivyde/faq.html
URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/faq.html?rev=699819&r1=699818&r2=699819&view=diff
==============================================================================
--- ant/ivy/site/target/ivyde/faq.html (original)
+++ ant/ivy/site/target/ivyde/faq.html Sun Sep 28 07:04:49 2008
@@ -69,7 +69,7 @@
<div class="block block-book" id="block-book-0">
<h2>IvyDE</h2>
- <div class="content"><ul id="treemenu" class="treeview"><li id="xooki-index" class="submenu"><a href="index.html" >Home</a><ul class="open"><li id="xooki-faq"><a href="faq.html" class="current">FAQ</a></li></ul></li><li id="xooki-download"><a href="download.html" >Download</a></li><li id="xooki-history/latest-milestone/index" class="submenu"><a href="history/latest-milestone/index.html" >Documentation (2.0.0.alpha1)</a><ul class="closed"><li id="xooki-history/latest-milestone/editor"><a href="history/latest-milestone/editor.html" >Editor</a></li><li id="xooki-history/latest-milestone/cp_container"><a href="history/latest-milestone/cp_container.html" >Classpath Container</a></li><li id="xooki-history/latest-milestone/maven"><a href="history/latest-milestone/maven.html" >Use with maven poms</a></li><li id="xooki-history/latest-milestone/console"><a href="history/latest-milestone/console.html" >Ivy Console</a></li><li id="xooki-history/latest-milestone/build"><a href="history
/latest-milestone/build.html" >Building IvyDE</a></li></ul></li><li id="xooki-history" class="submenu"><a href="history.html" >History</a><ul class="closed"><li id="xooki-history/trunk/index" class="submenu"><a href="history/trunk/index.html" >trunk</a><ul class="closed"><li id="xooki-history/trunk/editor"><a href="history/trunk/editor.html" >Editor</a></li><li id="xooki-history/trunk/cp_container"><a href="history/trunk/cp_container.html" >Classpath Container</a></li><li id="xooki-history/trunk/maven"><a href="history/trunk/maven.html" >Use with maven poms</a></li><li id="xooki-history/trunk/console"><a href="history/trunk/console.html" >Ivy Console</a></li><li id="xooki-history/trunk/build"><a href="history/trunk/build.html" >Building IvyDE</a></li></ul></li><li id="xooki-2.x" class="submenu">2.x<ul class="closed"><li id="xooki-history/2.0" class="submenu">2.0.x<ul class="closed"><li id="xooki-history/2.0.0.alpha1/index" class="submenu"><a href="history/2.0.0.alpha1/index.
html" >2.0.0.alpha1</a><ul class="closed"><li id="xooki-history/2.0.0.alpha1/editor"><a href="history/2.0.0.alpha1/editor.html" >Editor</a></li><li id="xooki-history/2.0.0.alpha1/cp_container"><a href="history/2.0.0.alpha1/cp_container.html" >Classpath Container</a></li><li id="xooki-history/2.0.0.alpha1/maven"><a href="history/2.0.0.alpha1/maven.html" >Use with maven poms</a></li><li id="xooki-history/2.0.0.alpha1/console"><a href="history/2.0.0.alpha1/console.html" >Ivy Console</a></li><li id="xooki-history/2.0.0.alpha1/build"><a href="history/2.0.0.alpha1/build.html" >Building IvyDE</a></li></ul></li></ul></li></ul></li><li id="xooki-history/1.2.0/index" class="submenu"><a href="history/1.2.0/index.html" >1.2.0</a><ul class="closed"><li id="xooki-history/1.2.0/editor"><a href="history/1.2.0/editor.html" >Editor</a></li><li id="xooki-history/1.2.0/cp_container"><a href="history/1.2.0/cp_container.html" >Classpath Container</a></li><li id="xooki-history/1.2.0/maven"><a href
="history/1.2.0/maven.html" >Use with maven poms</a></li></ul></li></ul></li><li id="xooki-get-involved" class="submenu"><a href="get-involved.html" >Get Involved</a><ul class="closed"><li id="xooki-mailing-lists"><a href="mailing-lists.html" >Mailing Lists</a></li><li id="xooki-issues"><a href="issues.html" >Issue Tracking</a></li></ul></li></ul></div>
+ <div class="content"><ul id="treemenu" class="treeview"><li id="xooki-index" class="submenu"><a href="index.html" >Home</a><ul class="open"><li id="xooki-faq"><a href="faq.html" class="current">FAQ</a></li></ul></li><li id="xooki-download"><a href="download.html" >Download</a></li><li id="xooki-history/latest-milestone/index" class="submenu"><a href="history/latest-milestone/index.html" >Documentation (2.0.0.alpha1)</a><ul class="closed"><li id="xooki-history/latest-milestone/editor"><a href="history/latest-milestone/editor.html" >Editor</a></li><li id="xooki-history/latest-milestone/cp_container"><a href="history/latest-milestone/cp_container.html" >Classpath Container</a></li><li id="xooki-history/latest-milestone/maven"><a href="history/latest-milestone/maven.html" >Use with maven poms</a></li><li id="xooki-history/latest-milestone/console"><a href="history/latest-milestone/console.html" >Ivy Console</a></li><li id="xooki-history/latest-milestone/build"><a href="history
/latest-milestone/build.html" >Building IvyDE</a></li></ul></li><li id="xooki-history" class="submenu"><a href="history.html" >History</a><ul class="closed"><li id="xooki-history/trunk/index" class="submenu"><a href="history/trunk/index.html" >trunk</a><ul class="closed"><li id="xooki-history/trunk/editor"><a href="history/trunk/editor.html" >Editor</a></li><li id="xooki-history/trunk/cp_container"><a href="history/trunk/cp_container.html" >Classpath Container</a></li><li id="xooki-history/trunk/maven"><a href="history/trunk/maven.html" >Use with maven poms</a></li><li id="xooki-history/trunk/console"><a href="history/trunk/console.html" >Ivy Console</a></li><li id="xooki-history/trunk/dev" class="submenu"><a href="history/trunk/dev.html" >Developer doc</a><ul class="closed"><li id="xooki-history/trunk/dev/build"><a href="history/trunk/dev/build.html" >Building</a></li><li id="xooki-history/trunk/dev/release"><a href="history/trunk/dev/release.html" >Releasing</a></li></ul><
/li></ul></li><li id="xooki-2.x" class="submenu">2.x<ul class="closed"><li id="xooki-history/2.0" class="submenu">2.0.x<ul class="closed"><li id="xooki-history/2.0.0.alpha1/index" class="submenu"><a href="history/2.0.0.alpha1/index.html" >2.0.0.alpha1</a><ul class="closed"><li id="xooki-history/2.0.0.alpha1/editor"><a href="history/2.0.0.alpha1/editor.html" >Editor</a></li><li id="xooki-history/2.0.0.alpha1/cp_container"><a href="history/2.0.0.alpha1/cp_container.html" >Classpath Container</a></li><li id="xooki-history/2.0.0.alpha1/maven"><a href="history/2.0.0.alpha1/maven.html" >Use with maven poms</a></li><li id="xooki-history/2.0.0.alpha1/console"><a href="history/2.0.0.alpha1/console.html" >Ivy Console</a></li><li id="xooki-history/2.0.0.alpha1/build"><a href="history/2.0.0.alpha1/build.html" >Building IvyDE</a></li></ul></li></ul></li></ul></li><li id="xooki-history/1.2.0/index" class="submenu"><a href="history/1.2.0/index.html" >1.2.0</a><ul class="closed"><li id="xoo
ki-history/1.2.0/editor"><a href="history/1.2.0/editor.html" >Editor</a></li><li id="xooki-history/1.2.0/cp_container"><a href="history/1.2.0/cp_container.html" >Classpath Container</a></li><li id="xooki-history/1.2.0/maven"><a href="history/1.2.0/maven.html" >Use with maven poms</a></li></ul></li></ul></li><li id="xooki-get-involved" class="submenu"><a href="get-involved.html" >Get Involved</a><ul class="closed"><li id="xooki-mailing-lists"><a href="mailing-lists.html" >Mailing Lists</a></li><li id="xooki-issues"><a href="issues.html" >Issue Tracking</a></li></ul></li></ul></div>
</div>
@@ -80,13 +80,13 @@
<h1 class="title">FAQ</h1>
<br class="xooki-br"/><ol>
- <li><a href="#duplicate-entries">What does the warning "There are some duplicates entries due to conflicts between the resolved configurations" means?</a><br class="xooki-br"/> <li><a href="#logs">Something goes wrong with IvyDE, where could I found more logs</a><br class="xooki-br"/> <li><a href="#empty-container">The IvyDE classpath container disappear when it becomes empty</a><br class="xooki-br"/></ol>
+ <li><a href="#duplicate-entries">What does the warning "There are some duplicates entries due to conflicts between the resolved configurations" means ?</a><br class="xooki-br"/> <li><a href="#logs">Something goes wrong with IvyDE, where could I found more logs ?</a><br class="xooki-br"/> <li><a href="#empty-container">The IvyDE classpath container disappear when it becomes empty</a><br class="xooki-br"/> <li><a href="#wtp">How can I make IvyDE contribute to the classpath used by WTP when launching my web application ?</a><br class="xooki-br"/></ol>
<br/>
-<h2><a name="duplicate-entries"></a>What does the warning "There are some duplicates entries due to conflicts between the resolved configurations" means?</h2>
+<h2><a name="duplicate-entries"></a>What does the warning "There are some duplicates entries due to conflicts between the resolved configurations" means ?</h2>
-The warning you get is about a module which you are trying to get in two different configurations. Ivy does the resolve and evict conflicts for only one configuration at a time. The resolve process is one by one configuration. If you have a use case where you have to build a classpath with a lot of different configuration, then you should consider having a new configuration that extends the other ones. Although in most case I think the configurations themselves should be fixed.<br class="xooki-br"/>For instance in Eclipse you might want to resolve 3 kinds of configuration: compile, test, and runtime. And then you get the warning, because test and runtime conflicts on one dependency. So this means that the ant target that will run the tests (after doing a resolve only on the test configuration) will actually use a different version of a dependency from the one used at runtime, from the one use by the ant target which build the jar. So tests are not running in the same environ
ment as the runtime one. Then you should fix the dependencies by having a direct dependency on the module that generated the conflict. Actually you might want to introduce a private "core" configuration, which will resolve the problematic dependency, and then make "runtime" and "test" extends that "core" configuration.<br class="xooki-br"/><br class="xooki-br"/>The topic has been also discussed on the <a href="http://mail-archives.apache.org/mod_mbox/ant-dev/200801.mbox/%3c5D017C51-ED7A-4A43-BBCA-08F291F4D92C@anyware-tech.com%3e">ant-dev mailing list</a>.<br class="xooki-br"/><br class="xooki-br"/><h2><a name="logs"></a>Something goes wrong with IvyDE, where could I found more logs</h2>
+The warning you get is about a module which you are trying to get in two different configurations. Ivy does the resolve and evict conflicts for only one configuration at a time. The resolve process is one by one configuration. If you have a use case where you have to build a classpath with a lot of different configuration, then you should consider having a new configuration that extends the other ones. Although in most case I think the configurations themselves should be fixed.<br class="xooki-br"/>For instance in Eclipse you might want to resolve 3 kinds of configuration: compile, test, and runtime. And then you get the warning, because test and runtime conflicts on one dependency. So this means that the ant target that will run the tests (after doing a resolve only on the test configuration) will actually use a different version of a dependency from the one used at runtime, from the one use by the ant target which build the jar. So tests are not running in the same environ
ment as the runtime one. Then you should fix the dependencies by having a direct dependency on the module that generated the conflict. Actually you might want to introduce a private "core" configuration, which will resolve the problematic dependency, and then make "runtime" and "test" extends that "core" configuration.<br class="xooki-br"/><br class="xooki-br"/>The topic has been also discussed on the <a href="http://mail-archives.apache.org/mod_mbox/ant-dev/200801.mbox/%3c5D017C51-ED7A-4A43-BBCA-08F291F4D92C@anyware-tech.com%3e">ant-dev mailing list</a>.<br class="xooki-br"/><br class="xooki-br"/><h2><a name="logs"></a>Something goes wrong with IvyDE, where could I found more logs ?</h2>
You can first look into the <a href="history/latest-milestone/console.html">IvyConsole</a><br class="xooki-br"/><br class="xooki-br"/>If you are running with the SDK version of Eclipse, you can find every Eclipse plugins log in the "Error log" view. You can open this view within the Menu <i>Window > Show View > Other...</i> and select the "Error Log" view in the "PDE Runtime" category.<br class="xooki-br"/><br class="xooki-br"/>Otherwise, you should look to the log file in your workspace: workspace/.metadata/.log<br class="xooki-br"/><br class="xooki-br"/><h2><a name="empty-container"></a>The IvyDE classpath container disappear when it becomes empty</h2>
@@ -100,7 +100,9 @@
<li>since Eclipse 3.4 you can configure that filter: enter the configuration panel of the filters of the package explorer and deselect the entry "Empty library containers".</li>
</ul>
+<h2><a name="wtp"></a>How can I make IvyDE contribute to the classpath used by WTP when launching my web application ?</h2>
+WTP is the <a href="http://www.eclipse.org/webtools/">Web Tools Plateform</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.<br class="xooki-br"/><br class="xooki-br"/>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.<br class="xooki-br"/><br class="xooki-br"/>This has been successfully tested with Eclipse 3.3 and WTP 2.0, Eclipse 3.4 and WTP 3.0.<br class="xooki-br"/><br class="xooki-br"/><br class="xooki-br"/>
<hr/>
<a href="?action=print">Printer Friendly</a>
</div><!-- main -->