ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hi...@apache.org
Subject svn commit: r682193 - /ant/ivy/site/ivyde/faq.html
Date Sun, 03 Aug 2008 16:43:01 GMT
Author: hibou
Date: Sun Aug  3 09:43:01 2008
New Revision: 682193

URL: http://svn.apache.org/viewvc?rev=682193&view=rev
Log:
Add some doc about the workaround of the empty containers

Modified:
    ant/ivy/site/ivyde/faq.html

Modified: ant/ivy/site/ivyde/faq.html
URL: http://svn.apache.org/viewvc/ant/ivy/site/ivyde/faq.html?rev=682193&r1=682192&r2=682193&view=diff
==============================================================================
--- ant/ivy/site/ivyde/faq.html (original)
+++ ant/ivy/site/ivyde/faq.html Sun Aug  3 09:43:01 2008
@@ -25,6 +25,14 @@
 </head>
 <body>
 	<textarea id="xooki-source">
+<ol>
+   <li><a href="#duplicate-entries">What does the warning "There are some duplicates
entries due to conflicts between the resolved configurations" means?</a>
+   <li><a href="#logs">Something goes wrong with IvyDE, where could I found more
logs</a>
+   <li><a href="#empty-container">The IvyDE classpath container disappear when
it becomes empty</a>
+</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>
 
 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.
@@ -40,6 +48,18 @@
 
 Otherwise, you should look to the log file in your workspace: workspace/.metadata/.log
 
+<h2><a name="empty-container"></a>The IvyDE classpath container disappear
when it becomes empty</h2>
+
+Since Eclipse 3.3, when a classpath container contains no entry, Eclipse makes it disappear.
As the IvyDE context menu can only be triggered on the IvyDE container, if it disappears,
the user is not able to easily manage its container. It has been decided (<a href="http://issues.apache.org/jira/browse/IVYDE-82">IVYDE-82</a>)
to not try to fix it as this behavior is hard coded in the deep code of Eclipse, and that
there is a workaround:
+<ul><li>with Eclipse 3.3, to configure Ivy and trigger a resolve:<ul>
+    <li>enter the configuration panel of the build path of your project</li>
+    <li>enter in the "Libraries" tab</li>
+    <li>select the IvyDE container and click the button "edit": you enter in the configuration
panel of your container</li>
+    </li></ul>
+Then as soon as you save the configuration of your IvyDE container (by clicking on "finish"),
a resolve will be triggered automatically. 
+<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>
+
 </textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>



Mime
View raw message