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>. 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. <h1><a name="global"></a>Global Ivy preferences</h1> <center><img src="images/pref.jpg"/></center> <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> <h1><a name="classpath"></a>Classpath configuration</h1> <center><img src="images/pref_classpath.jpg"/></center> <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> <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> <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> <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>