ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hi...@apache.org
Subject svn commit: r667204 - /ant/ivy/site/ivyde/faq.html
Date Thu, 12 Jun 2008 19:12:45 GMT
Author: hibou
Date: Thu Jun 12 12:12:45 2008
New Revision: 667204

URL: http://svn.apache.org/viewvc?rev=667204&view=rev
Log:
Add an faq item about the logs of IvyDE

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=667204&r1=667203&r2=667204&view=diff
==============================================================================
--- ant/ivy/site/ivyde/faq.html (original)
+++ ant/ivy/site/ivyde/faq.html Thu Jun 12 12:12:45 2008
@@ -25,12 +25,21 @@
 </head>
 <body>
 	<textarea id="xooki-source">
-<h2>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 conflits 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.
+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.
 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 environment 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.
 
 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>.
+
+<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>
+
+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.
+
+Otherwise, you should look to the log file in your workspace: workspace/.metadata/.log
+
 </textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>



Mime
View raw message