You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by xa...@apache.org on 2007/03/19 13:14:33 UTC
svn commit: r519939 [3/4] - in /incubator/ivy/core/trunk: ./ doc/ doc/doc/
doc/doc/configuration/ doc/doc/tutorial/ doc/doc/tutorial/build-repository/
doc/doc/use/
Modified: incubator/ivy/core/trunk/doc/doc/tutorial/defaultconf.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/tutorial/defaultconf.html?view=diff&rev=519939&r1=519938&r2=519939
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/tutorial/defaultconf.html (original)
+++ incubator/ivy/core/trunk/doc/doc/tutorial/defaultconf.html Mon Mar 19 06:14:32 2007
@@ -5,194 +5,194 @@
<script type="text/javascript" src="../../xooki/xooki.js"></script>
</head>
<body>
- <textarea id="xooki-source">
-Until Ivy 1.2a, the default resolver was a simple ivyrep resolver, with only a small number of possibilities of configuration. Whenever you wanted to do something slightly more complicated than looking for ivy files on ivyrep and artifacts on ibiblio, you had to write your own ivysettings file (see other tutorials and <a href="../../doc/configuration.html">configuration</a> reference for details about this).
-
-Ivy 1.3 introduces a new default configuration, fully compatible pre 1.3 one, but a lot more configurable.
-
-<h1>Concept</h1>
-This default configuration mainly consists of 3 kind of repositories:
-<ul>
-<li>local</li> a repository which is private to the user.
-<li>shared</li> a repository which is shared between all the member of a team
-<li>public</li> a public repository on which most modules can be found
-</ul>
-
-Note that if you work alone, the distinction between local and shared repository is not very important, but there are some things to know to distinguish them.
-
-Now let's describe each of these repositories concept in more details. We will describe how they are setup physically later.
-<h2>Local</h2>
-The local repository is particularly useful when you want to do something without being disturb by anything else happening in the environment. This means that whenever ivy is able to locate a module in this repository it will be used, no matter of what is available in others.
-
-For instance, if you have a module declaring a dependency on the module foo in revision latest.integration, then if a revision of foo is found in the local repository, it will be used, <em>even if a more recent revision is available in other repositories</em>.
-
-This may be disturbing for some of you, but imagine you have to implement a new feature on a project, and in order to achieve that you need to modify two modules: you add a new method in module foo and exploit this new method in module bar. Then if you publish the module foo to your local repository, you will be sure to get it in your bar module, even if someone else publish a new revision of foo in the shared repository (this revision not having the new method you are currently adding).
-
-But be careful, when you have finished your development and publish it on the shared you will have to clean your local repository to benefit from new versions published in the shared repository.
-
-Note also that modules found in the local repository must be complete, i.e. they must provide both a module descriptor and the published artifacts.
-<h2>Shared</h2>
-As its name suggest, the shared repository is aimed to be shared among a whole development team. It is a place where you can publish your team private modules for instance, and it's also a place where you can put modules not available in the public repository (sun jars, for instance), or simply not accurate (bad or incomplete module descriptors for instance).
-
-Note that modules can be split across the shared repository and the public one: you can have the module descritor in the shared repository and the artifacts in the public one, for instance.
-<h2>Public</h2>
-The public repository is the place where most modules can be found, but which sometimes lack the information you need. It's usually a repository available through an internet connection only, even if this is not mandatory.
-<h1>Setting up the repositories</h1>
-Now that we have seen the objective of each of the three repositories, let's see how they are setup and how to configure them to fit your needs.
-
-First, several repositories uses the same root in your filesystem. Referenced as ${ivy.default.ivy.user.dir}, this is by default the directory .ivy in your user home.
-
-Note that several things can be done by setting ivy variable. To set them without defining your own ivysettings.xml file, you can:<ul>
-<li>set an ant property before any call to ivy in your build file if you use ivy from ant</li>
-<li>set an environment variable if you use ivy from the command line</li>
-</ul>
-For instance:
-<code type="xml">
-<target name="resolve">
- <property name="ivy.default.ivy.user.dir" value="/path/to/ivy/user/dir"/>
- <ivy:resolve />
-</target>
-</code>
-
-Now we will show how to override default values for the different kind of repositories, note that you can find what are these default values below in the detail of the default configuration.
-<h2>Local</h2>
-By default, the local repository lies in ${ivy.default.ivy.user.dir}/local. This is usually a good place, but you may want to modify it however. No problem, you just have to set the following ivy variable to the directory you want to use: <code>ivy.local.default.root</code>. For instance:
-<code>ivy.local.default.root=/opt/ivy/repository/local</code>.
-
-If you already have something you would like to use as your local repository, you may also want to modify the layout of this repository. Once again, two variables are available for that:
-<code>ivy.local.default.ivy.pattern</code> gives the pattern to find ivy files
-<code>ivy.local.default.artifact.pattern</code> gives the pattern to find artifacts
-For example:
-<code>
-ivy.local.default.root=/opt/ivy/repository/local
-ivy.local.default.ivy.pattern=[module]/[revision]/ivy.xml
-ivy.local.default.artifact.pattern=[module]/[revision]/[artifact].[ext]
-</code>
-<h2>Shared</h2>
-By default, the shared repository lies in ${ivy.default.ivy.user.dir}/shared. This is fine if you work alone, but the shared repository is supposed to be, mmm, shared ! So changing this directory is often required, and it is usually modified to point to a shared directory. You can use <code>ivy.shared.default.root</code> variable to specify in a new directory. Moreover, you can also configure the layout with variables similar to the one for the local repository:
-<code>ivy.shared.default.ivy.pattern</code> gives the pattern to find ivy files
-<code>ivy.shared.default.artifact.pattern</code> gives the pattern to find artifacts
-For example:
-<code>
-ivy.shared.default.root=/opt/ivy/repository/shared
-ivy.shared.default.ivy.pattern=[organisation]/[module]/[revision]/ivy.xml
-ivy.shared.default.artifact.pattern=[organisation]/[module]/[revision]/[artifact].[ext]
-</code>
-
-<h2>Public</h2>
-By default, the public repository is ivyrep. To change the setting of this resolver, you can use the standard way to configure ivyrep:
-<code>ivy.ivyrep.default.ivy.root</code> specify the root for ivy files
-<code>ivy.ivyrep.default.ivy.pattern</code> specify the layout for ivy files
-<code>ivy.ivyrep.default.artifact.root</code> specify the root for artifacts
-<code>ivy.ivyrep.default.artifact.pattern</code> specify the layout for artifacts
-For instance:
-<code>
-ivy.ivyrep.default.ivy.root=http://myserver/ivy/
-ivy.ivyrep.default.artifact.root=http://myserver/ivy/
-</code>
-
-<h1>Going further</h1>
-OK, so we have seen how to easily change the settings of the three main repositories. But what if I want my shared repository is on a web server ? What if the public repository is not compatible with ivyrep ? What if ...
-
-Everything can be changed in the default configuration, for sure, you can even do your own configuration. But you can also benefit from a part of the default configuration without writing a complete one.
-
-But before explaining how, you will need to have a quick overview of how ivy is configured by default.
-
-By default, ivy is configured using an ivysettings.xml which is packaged in the ivy jar. Here is this ivysettings file:
-<code type="xml">
-<ivysettings>
- <conf defaultResolver="default"/>
- <include url="${ivy.default.conf.dir}/ivysettings-public.xml"/>
- <include url="${ivy.default.conf.dir}/ivysettings-shared.xml"/>
- <include url="${ivy.default.conf.dir}/ivysettings-local.xml"/>
- <include url="${ivy.default.conf.dir}/ivysettings-main-chain.xml"/>
- <include url="${ivy.default.conf.dir}/ivysettings-default-chain.xml"/>
-</ivysettings>
-</code>
-OK, so not much info here, except a lot of inclusions. These inclusions have been done on purpose so that you can easily change only one part of the ivysettings and benefit of the rest easily. For example, if you want to define your own public resolver, you will just have to configure ivy with an ivysettings like that:
-<code type="xml">
-<ivysettings>
- <conf defaultResolver="default"/>
- <include url="http://myserver/ivy/myivysettings-public.xml"/>
- <include url="${ivy.default.conf.dir}/ivysettings-shared.xml"/>
- <include url="${ivy.default.conf.dir}/ivysettings-local.xml"/>
- <include url="${ivy.default.conf.dir}/ivysettings-main-chain.xml"/>
- <include url="${ivy.default.conf.dir}/ivysettings-default-chain.xml"/>
-</ivysettings>
-</code>
-Note that only the ivysettings-public inclusion has changed to include a home made public resolver. Note also that this can be used like that thanks to the fact that ${ivy.default.conf.dir} is a variable which is always set to the place where ivy default configuration files are (i.e. packaged in the jar).
-To finish this example, you for sure have to write your own ivysettings file for defining your own public resolver. For instance:
-<code type="xml">
-<ivysettings>
- <resolvers>
- <filesystem name="public">
- <ivy pattern="/path/to/my/public/rep/[organisation]/[module]/ivy-[revision].xml" />
- <artifact pattern="/path/to/my/public/rep/[organisation]/[module]/[artifact]-[revision].[ext]" />
- </filesystem>
- </resolvers>
-</ivysettings>
-</code>
-No the last thing you will need in order to properly take advantage of the default configuration is the content of each included ivysettings file:
-<strong>ivysettings-public.xml</strong>
-<code type="xml">
-<ivysettings>
- <resolvers>
- <ivyrep name="public"/>
- </resolvers>
-</ivysettings>
-</code>
-<strong>ivysettings-shared.xml</strong>
-<code type="xml">
-<ivysettings>
- <property name="ivy.shared.default.root" value="${ivy.default.ivy.user.dir}/shared" override="false"/>
- <property name="ivy.shared.default.ivy.pattern" value="[organisation]/[module]/[revision]/[type]s/[artifact].[ext]" override="false"/>
- <property name="ivy.shared.default.artifact.pattern" value="[organisation]/[module]/[revision]/[type]s/[artifact].[ext]" override="false"/>
- <resolvers>
- <filesystem name="shared">
- <ivy pattern="${ivy.shared.default.root}/${ivy.shared.default.ivy.pattern}" />
- <artifact pattern="${ivy.shared.default.root}/${ivy.shared.default.artifact.pattern}" />
- </filesystem>
- </resolvers>
-</ivysettings>
-</code>
-<strong>ivysettings-local.xml</strong>
-<code type="xml">
-<ivysettings>
- <property name="ivy.local.default.root" value="${ivy.default.ivy.user.dir}/local" override="false"/>
- <property name="ivy.local.default.ivy.pattern" value="[organisation]/[module]/[revision]/[type]s/[artifact].[ext]" override="false"/>
- <property name="ivy.local.default.artifact.pattern" value="[organisation]/[module]/[revision]/[type]s/[artifact].[ext]" override="false"/>
- <resolvers>
- <filesystem name="local">
- <ivy pattern="${ivy.local.default.root}/${ivy.local.default.ivy.pattern}" />
- <artifact pattern="${ivy.local.default.root}/${ivy.local.default.artifact.pattern}" />
- </filesystem>
- </resolvers>
-</ivysettings>
-</code>
-<strong>ivysettings-main-chain.xml</strong>
-<code type="xml">
-<ivysettings>
- <resolvers>
- <chain name="main" dual="true">
- <resolver ref="shared"/>
- <resolver ref="public"/>
- </chain>
- </resolvers>
-</ivysettings>
-</code>
-<strong>ivysettings-default-chain.xml</strong>
-<code type="xml">
-<ivysettings>
- <resolvers>
- <chain name="default" returnFirst="true">
- <resolver ref="local"/>
- <resolver ref="main"/>
- </chain>
- </resolvers>
-</ivysettings>
-</code>
-
-Here you are, you have enough clues to configure that the way you want... check the <a href="../../doc/configuration.html">configuration documentation</a> to see if what you want to do is possible, and go ahead !
+ <textarea id="xooki-source">
+Until Ivy 1.2a, the default resolver was a simple ivyrep resolver, with only a small number of possibilities of configuration. Whenever you wanted to do something slightly more complicated than looking for ivy files on ivyrep and artifacts on ibiblio, you had to write your own ivysettings file (see other tutorials and <a href="../../doc/configuration.html">settings</a> reference for details about this).
+
+Ivy 1.3 introduced new default settings a lot more flexible.
+
+<h1>Concept</h1>
+This default settings mainly consist of 3 kind of repositories:
+<ul>
+<li>local</li> a repository which is private to the user.
+<li>shared</li> a repository which is shared between all the member of a team
+<li>public</li> a public repository on which most modules can be found
+</ul>
+
+Note that if you work alone, the distinction between local and shared repository is not very important, but there are some things to know to distinguish them.
+
+Now let's describe each of these repositories concept in more details. We will describe how they are setup physically later.
+<h2>Local</h2>
+The local repository is particularly useful when you want to do something without being disturb by anything else happening in the environment. This means that whenever ivy is able to locate a module in this repository it will be used, no matter of what is available in others.
+
+For instance, if you have a module declaring a dependency on the module foo in revision latest.integration, then if a revision of foo is found in the local repository, it will be used, <em>even if a more recent revision is available in other repositories</em>.
+
+This may be disturbing for some of you, but imagine you have to implement a new feature on a project, and in order to achieve that you need to modify two modules: you add a new method in module foo and exploit this new method in module bar. Then if you publish the module foo to your local repository, you will be sure to get it in your bar module, even if someone else publish a new revision of foo in the shared repository (this revision not having the new method you are currently adding).
+
+But be careful, when you have finished your development and publish it on the shared you will have to clean your local repository to benefit from new versions published in the shared repository.
+
+Note also that modules found in the local repository must be complete, i.e. they must provide both a module descriptor and the published artifacts.
+<h2>Shared</h2>
+As its name suggest, the shared repository is aimed to be shared among a whole development team. It is a place where you can publish your team private modules for instance, and it's also a place where you can put modules not available in the public repository (sun jars, for instance), or simply not accurate (bad or incomplete module descriptors for instance).
+
+Note that modules can be split across the shared repository and the public one: you can have the module descritor in the shared repository and the artifacts in the public one, for instance.
+<h2>Public</h2>
+The public repository is the place where most modules can be found, but which sometimes lack the information you need. It's usually a repository available through an internet connection only, even if this is not mandatory.
+<h1>Setting up the repositories</h1>
+Now that we have seen the objective of each of the three repositories, let's see how they are setup and how to configure them to fit your needs.
+
+First, several repositories uses the same root in your filesystem. Referenced as ${ivy.default.ivy.user.dir}, this is by default the directory .ivy in your user home.
+
+Note that several things can be done by setting ivy variable. To set them without defining your own ivysettings.xml file, you can:<ul>
+<li>set an ant property before any call to ivy in your build file if you use ivy from ant</li>
+<li>set an environment variable if you use ivy from the command line</li>
+</ul>
+For instance:
+<code type="xml">
+<target name="resolve">
+ <property name="ivy.default.ivy.user.dir" value="/path/to/ivy/user/dir"/>
+ <ivy:resolve />
+</target>
+</code>
+
+Now we will show how to override default values for the different kind of repositories, note that you can find what are these default values below in the detail of the default settings.
+<h2>Local</h2>
+By default, the local repository lies in ${ivy.default.ivy.user.dir}/local. This is usually a good place, but you may want to modify it however. No problem, you just have to set the following ivy variable to the directory you want to use: <code>ivy.local.default.root</code>. For instance:
+<code>ivy.local.default.root=/opt/ivy/repository/local</code>.
+
+If you already have something you would like to use as your local repository, you may also want to modify the layout of this repository. Once again, two variables are available for that:
+<code>ivy.local.default.ivy.pattern</code> gives the pattern to find ivy files
+<code>ivy.local.default.artifact.pattern</code> gives the pattern to find artifacts
+For example:
+<code>
+ivy.local.default.root=/opt/ivy/repository/local
+ivy.local.default.ivy.pattern=[module]/[revision]/ivy.xml
+ivy.local.default.artifact.pattern=[module]/[revision]/[artifact].[ext]
+</code>
+<h2>Shared</h2>
+By default, the shared repository lies in ${ivy.default.ivy.user.dir}/shared. This is fine if you work alone, but the shared repository is supposed to be, mmm, shared! So changing this directory is often required, and it is usually modified to point to a shared directory. You can use <code>ivy.shared.default.root</code> variable to specify in a new directory. Moreover, you can also configure the layout with variables similar to the one for the local repository:
+<code>ivy.shared.default.ivy.pattern</code> gives the pattern to find ivy files
+<code>ivy.shared.default.artifact.pattern</code> gives the pattern to find artifacts
+For example:
+<code>
+ivy.shared.default.root=/opt/ivy/repository/shared
+ivy.shared.default.ivy.pattern=[organisation]/[module]/[revision]/ivy.xml
+ivy.shared.default.artifact.pattern=[organisation]/[module]/[revision]/[artifact].[ext]
+</code>
+
+<h2>Public</h2>
+By default, the public repository is ivyrep. To change the setting of this resolver, you can use the standard way to configure ivyrep:
+<code>ivy.ivyrep.default.ivy.root</code> specify the root for ivy files
+<code>ivy.ivyrep.default.ivy.pattern</code> specify the layout for ivy files
+<code>ivy.ivyrep.default.artifact.root</code> specify the root for artifacts
+<code>ivy.ivyrep.default.artifact.pattern</code> specify the layout for artifacts
+For instance:
+<code>
+ivy.ivyrep.default.ivy.root=http://myserver/ivy/
+ivy.ivyrep.default.artifact.root=http://myserver/ivy/
+</code>
+
+<h1>Going further</h1>
+OK, so we have seen how to easily change the settings of the three main repositories. But what if I want my shared repository is on a web server ? What if the public repository is not compatible with ivyrep ? What if ...
+
+Everything can be changed in the default settings, for sure, you can even do your own settings. But you can also benefit from a part of the default settings without writing a complete one.
+
+But before explaining how, you will need to have a quick overview of how ivy is configured by default.
+
+By default, ivy is configured using an ivysettings.xml which is packaged in the ivy jar. Here is this settings file:
+<code type="xml">
+<ivysettings>
+ <settings defaultResolver="default"/>
+ <include url="${ivy.default.conf.dir}/ivysettings-public.xml"/>
+ <include url="${ivy.default.conf.dir}/ivysettings-shared.xml"/>
+ <include url="${ivy.default.conf.dir}/ivysettings-local.xml"/>
+ <include url="${ivy.default.conf.dir}/ivysettings-main-chain.xml"/>
+ <include url="${ivy.default.conf.dir}/ivysettings-default-chain.xml"/>
+</ivysettings>
+</code>
+OK, so not much info here, except a lot of inclusions. These inclusions have been done on purpose so that you can easily change only one part of the ivysettings and benefit of the rest easily. For example, if you want to define your own public resolver, you will just have to configure ivy with an ivysettings like that:
+<code type="xml">
+<ivysettings>
+ <settings defaultResolver="default"/>
+ <include url="http://myserver/ivy/myivysettings-public.xml"/>
+ <include url="${ivy.default.settings.dir}/ivysettings-shared.xml"/>
+ <include url="${ivy.default.settings.dir}/ivysettings-local.xml"/>
+ <include url="${ivy.default.settings.dir}/ivysettings-main-chain.xml"/>
+ <include url="${ivy.default.settings.dir}/ivysettings-default-chain.xml"/>
+</ivysettings>
+</code>
+Note that only the ivysettings-public inclusion has changed to include a home made public resolver. Note also that this can be used like that thanks to the fact that ${ivy.default.settings.dir} is a variable which is always set to the place where ivy default settings files are (i.e. packaged in the jar).
+To finish this example, you for sure have to write your own ivysettings file for defining your own public resolver. For instance:
+<code type="xml">
+<ivysettings>
+ <resolvers>
+ <filesystem name="public">
+ <ivy pattern="/path/to/my/public/rep/[organisation]/[module]/ivy-[revision].xml" />
+ <artifact pattern="/path/to/my/public/rep/[organisation]/[module]/[artifact]-[revision].[ext]" />
+ </filesystem>
+ </resolvers>
+</ivysettings>
+</code>
+No the last thing you will need in order to properly take advantage of the default settings is the content of each included ivysettings file:
+<strong>ivysettings-public.xml</strong>
+<code type="xml">
+<ivysettings>
+ <resolvers>
+ <ivyrep name="public"/>
+ </resolvers>
+</ivysettings>
+</code>
+<strong>ivysettings-shared.xml</strong>
+<code type="xml">
+<ivysettings>
+ <property name="ivy.shared.default.root" value="${ivy.default.ivy.user.dir}/shared" override="false"/>
+ <property name="ivy.shared.default.ivy.pattern" value="[organisation]/[module]/[revision]/[type]s/[artifact].[ext]" override="false"/>
+ <property name="ivy.shared.default.artifact.pattern" value="[organisation]/[module]/[revision]/[type]s/[artifact].[ext]" override="false"/>
+ <resolvers>
+ <filesystem name="shared">
+ <ivy pattern="${ivy.shared.default.root}/${ivy.shared.default.ivy.pattern}" />
+ <artifact pattern="${ivy.shared.default.root}/${ivy.shared.default.artifact.pattern}" />
+ </filesystem>
+ </resolvers>
+</ivysettings>
+</code>
+<strong>ivysettings-local.xml</strong>
+<code type="xml">
+<ivysettings>
+ <property name="ivy.local.default.root" value="${ivy.default.ivy.user.dir}/local" override="false"/>
+ <property name="ivy.local.default.ivy.pattern" value="[organisation]/[module]/[revision]/[type]s/[artifact].[ext]" override="false"/>
+ <property name="ivy.local.default.artifact.pattern" value="[organisation]/[module]/[revision]/[type]s/[artifact].[ext]" override="false"/>
+ <resolvers>
+ <filesystem name="local">
+ <ivy pattern="${ivy.local.default.root}/${ivy.local.default.ivy.pattern}" />
+ <artifact pattern="${ivy.local.default.root}/${ivy.local.default.artifact.pattern}" />
+ </filesystem>
+ </resolvers>
+</ivysettings>
+</code>
+<strong>ivysettings-main-chain.xml</strong>
+<code type="xml">
+<ivysettings>
+ <resolvers>
+ <chain name="main" dual="true">
+ <resolver ref="shared"/>
+ <resolver ref="public"/>
+ </chain>
+ </resolvers>
+</ivysettings>
+</code>
+<strong>ivysettings-default-chain.xml</strong>
+<code type="xml">
+<ivysettings>
+ <resolvers>
+ <chain name="default" returnFirst="true">
+ <resolver ref="local"/>
+ <resolver ref="main"/>
+ </chain>
+ </resolvers>
+</ivysettings>
+</code>
+
+Here you are, you have enough clues to configure that the way you want... check the <a href="../../doc/configuration.html">settings documentation</a> to see if what you want to do is possible, and go ahead !
</textarea>
<script type="text/javascript">xooki.postProcess();</script>
</body>
Modified: incubator/ivy/core/trunk/doc/doc/tutorial/dual.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/tutorial/dual.html?view=diff&rev=519939&r1=519938&r2=519939
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/tutorial/dual.html (original)
+++ incubator/ivy/core/trunk/doc/doc/tutorial/dual.html Mon Mar 19 06:14:32 2007
@@ -5,147 +5,146 @@
<script type="text/javascript" src="../../xooki/xooki.js"></script>
</head>
<body>
- <textarea id="xooki-source">
-This tutorial presents the use of the DualResolver, a feature introduced in the version 0.6 of Ivy.
-
-Dual Resolver is used when ivy files can be found in a repository while artifacts are in another. It is especially useful to use full power of ivy (including transitive dependencies) with the ibiblio repository for artifacts. The problem with the maven ibiblio repository is that it does not contain ivy files. Since transitive dependencies are based upon ivy files, using the ibiblio resolver does not permit to use transitive dependencies.
-
-The solution to this problem is to store your own repository only for ivy files, and use ibiblio for artifacts. That's what is done in this tutorial.
-
-<h1>project description</h1>
-Let's have a look at the src/example/dual directory in your ivy distribution.
-It contains a build file and 3 directories:
-<ul>
-<li>config: contains the ivy configuration file</li>
-<li>repository: a sample repository of ivy files</li>
-<li>project: the project making use of ivy with dual resolver</li>
-</ul>
-
-<h2>the dual project</h2>
-The project is very simple and contains only one test class : example.Hello
-It depends on two libraries: apache commons-lang and apache commons-httpclient.
-
-Here is the content of the project :
-<ul>
- <li>build.xml : the ant build file for the project</li>
- <li>ivy.xml : the ivy project file</li>
- <li>src\example\Hello.java : the only class of the project</li>
-</ul>
-Take a look at it's <b>ivy.xml</b> file:
-<code>
-<ivy-module version="1.0">
- <info organisation="jayasoft" module="hello-ivy" />
- <dependencies>
- <dependency org="apache" name="commons-httpclient" rev="2.0.2" />
- <dependency org="apache" name="commons-lang" rev="2.0" />
- </dependencies>
-</ivy-module>
-</code>
-
-As you can see, nothing special here... Indeed, it's the philosophy of ivy to keep ivy files independent of the way dependencies are retrieved.
-
-<h2>the <b>ivy</b> configuration</h2>
-The ivy configuration is made in the config directory it contains only one file: ivysettings.xml.
-
-Let's analyse it.
-<code>
-<ivysettings>
- <conf defaultResolver="dual-example" />
- <resolvers>
- <dual name="dual-example">
- <filesystem name="ivys">
- <ivy pattern="${ivy.settings.dir}/../repository/[module]-ivy-[revision].xml" />
- </filesystem>
- <ibiblio name="ibiblio" />
- </dual>
- </resolvers>
-</ivysettings>
-</code>
-
-Here we configure one resolver, the default one, which is a dual resolver. This dual resolver has two sub resolvers : the first is what is called the "ivy" resolver of the dual resolver, and the second one is what is called the "artifact" resolver. It is important that the dual resolver exactly has two sub resolvers in this given order.
-The ivy resolver, here a filesystem one, is used only to find ivy files. The configuration given in this resolver
-says that all ivy files are in the same directory, named like that: [module]-ivy-[revision].xml. If we check the repository directory, we can confirm that it contains a file named commons-httpclient-ivy-2.0.2.xml. It fulfills the given pattern and will thus be find by this resolver.
-The artifact resolver is simply an ibiblio one, and will thus try to find required artifacts in the maven ibiblio repository.
-
-<h1>walkthrough</h1>
-<div class="step">
-<h2>step 1 : preparation</h2>
-Open a DOS or shell window, and go to the "dual" directory.
-</div>
-<div class="step">
-<h2>step 2 : clean up</h2>
-On the prompt type : ant<br>
-This will clean up the entire project directory tree (compiled classes and retrieved libs) and ivy cache.
-You can do it each time you want to clean up this example.
-</div>
-<div class="step">
-<h2>step 3 : run the project</h2>
-Goto project directory. And simply run <b>ant</b>.
-<div class="shell"><pre>
-I:\dual\project>ant
-Buildfile: build.xml
-
-configure:
-:: Ivy 1.0-rc3 - 20050421161206 :: http://ivy.jayasoft.org/ ::
-
-resolve:
-:: resolving dependencies :: jayasoft/hello-ivy-working@xmen
- confs: [default]
-downloading http://www.ibiblio.org/maven/commons-lang/jars/commons-lang-2.0.jar(2.0) ...
-.....
-.........
-..........
-...........
-. (165kB)
- [SUCCESSFUL ] apache/commons-lang-2.0/commons-lang.jar[jar] (8032ms)
-downloading http://www.ibiblio.org/maven/commons-httpclient/jars/commons-httpclient-2.0.2.jar(2.0.2) ...
-...........
-......
-....
-..........
-............
-........ (220kB)
- [SUCCESSFUL ] apache/commons-httpclient-2.0.2/commons-httpclient.jar[jar] (10031ms)
-downloading http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.0.4.jar(1.0.4) ...
-......... (37kB)
- [SUCCESSFUL ] apache/commons-logging-1.0.4/commons-logging.jar[jar] (1469ms)
-:: resolution report ::
- ---------------------------------------------------------------------
- | | modules || artifacts |
- | conf | number| search|dwnlded|evicted|| number|dwnlded|
- ---------------------------------------------------------------------
- | default | 3 | 3 | 1 | 0 || 3 | 3 |
- ---------------------------------------------------------------------
-:: retrieving :: jayasoft/hello-ivy
- confs: [default]
- 3 artifacts copied, 0 already retrieved
-
-run:
- [mkdir] Created dir: I:\dual\project\build
- [javac] Compiling 1 source file to I:\dual\project\build
- [java] standard message : hello ivy !
- [java] capitalized by org.apache.commons.lang.WordUtils : Hello Ivy !
- [java] head status code with httpclient: 200
- [java] now check if httpclient dependency on commons-logging has been realized
- [java] found logging class in classpath: interface org.apache.commons.logging.Log
-
-BUILD SUCCESSFUL
-Total time: 24 seconds
-</pre></div></div>
-<br/>
-As you can see, ivy not only downloaded commons-lang and commons-httpclient, but also commons-logging. Indeed, commons-logging is a dependency of httpclient, as we can see in the httpclient ivy file found in the repository directory:
-<code>
-<ivy-module version="1.0">
- <info organisation="apache" module="commons-httpclient" revision="2.0.2" status="release" publication="20041010174300" />
- <dependencies>
- <dependency name="commons-logging" rev="1.0.4" conf="default" />
- </dependencies>
-</ivy-module>
-</code>
-<br/>
-So everything worked well, ivy file has been found in the repository directory and artifacts have been downloaded from ibiblio. You now just have to write ivy files for the module you often use, and they will be much easier to use... And imagine a world in which each module delivers also an ivy file. Since it is independent of the way to retrieve dependencies, it would made all dependencies handling much easier, wouldn't it ?
-
-
+ <textarea id="xooki-source">
+This tutorial presents the use of the DualResolver, a feature introduced in the version 0.6 of Ivy.
+
+Dual Resolver is used when ivy files can be found in a repository while artifacts are in another. It is especially useful to use full power of ivy (including transitive dependencies) with the ibiblio repository for artifacts. The problem with the maven ibiblio repository is that it does not contain ivy files. Since transitive dependencies are based upon ivy files, using the ibiblio resolver does not permit to use transitive dependencies.
+
+The solution to this problem is to store your own repository only for ivy files, and use ibiblio for artifacts. That's what is done in this tutorial.
+
+<h1>project description</h1>
+Let's have a look at the src/example/dual directory in your ivy distribution.
+It contains a build file and 3 directories:
+<ul>
+<li>config: contains the ivy settings file</li>
+<li>repository: a sample repository of ivy files</li>
+<li>project: the project making use of ivy with dual resolver</li>
+</ul>
+
+<h2>the dual project</h2>
+The project is very simple and contains only one test class : example.Hello
+It depends on two libraries: apache commons-lang and apache commons-httpclient.
+
+Here is the content of the project :
+<ul>
+ <li>build.xml : the ant build file for the project</li>
+ <li>ivy.xml : the ivy project file</li>
+ <li>src\example\Hello.java : the only class of the project</li>
+</ul>
+Take a look at it's <b>ivy.xml</b> file:
+<code>
+<ivy-module version="1.0">
+ <info organisation="jayasoft" module="hello-ivy" />
+ <dependencies>
+ <dependency org="apache" name="commons-httpclient" rev="2.0.2" />
+ <dependency org="apache" name="commons-lang" rev="2.0" />
+ </dependencies>
+</ivy-module>
+</code>
+
+As you can see, nothing special here... Indeed, it's the philosophy of ivy to keep ivy files independent of the way dependencies are retrieved.
+
+<h2>the <b>ivy</b> settings</h2>
+The ivy settings is made in the config directory it contains only one file: ivysettings.xml.
+
+Let's analyse it.
+<code>
+<ivysettings>
+ <settings defaultResolver="dual-example" />
+ <resolvers>
+ <dual name="dual-example">
+ <filesystem name="ivys">
+ <ivy pattern="${ivy.settings.dir}/../repository/[module]-ivy-[revision].xml" />
+ </filesystem>
+ <ibiblio name="ibiblio" />
+ </dual>
+ </resolvers>
+</ivysettings>
+</code>
+
+Here we configure one resolver, the default one, which is a dual resolver. This dual resolver has two sub resolvers: the first is what is called the "ivy" resolver of the dual resolver, and the second one is what is called the "artifact" resolver. It is important that the dual resolver exactly has two sub resolvers in this given order.
+The ivy resolver, here a filesystem one, is used only to find ivy files. The settings given in this resolver says that all ivy files are in the same directory, named like that: [module]-ivy-[revision].xml. If we check the repository directory, we can confirm that it contains a file named commons-httpclient-ivy-2.0.2.xml. It fulfills the given pattern and will thus be find by this resolver.
+The artifact resolver is simply an ibiblio one, and will thus try to find required artifacts in the maven ibiblio repository.
+
+<h1>walkthrough</h1>
+<div class="step">
+<h2>step 1 : preparation</h2>
+Open a DOS or shell window, and go to the "dual" directory.
+</div>
+<div class="step">
+<h2>step 2 : clean up</h2>
+On the prompt type : ant<br>
+This will clean up the entire project directory tree (compiled classes and retrieved libs) and ivy cache.
+You can do it each time you want to clean up this example.
+</div>
+<div class="step">
+<h2>step 3 : run the project</h2>
+Goto project directory. And simply run <b>ant</b>.
+<div class="shell"><pre>
+I:\dual\project>ant
+Buildfile: build.xml
+
+configure:
+:: Ivy 1.0-rc3 - 20050421161206 :: http://ivy.jayasoft.org/ ::
+
+resolve:
+:: resolving dependencies :: jayasoft/hello-ivy-working@xmen
+ confs: [default]
+downloading http://www.ibiblio.org/maven/commons-lang/jars/commons-lang-2.0.jar(2.0) ...
+.....
+.........
+..........
+...........
+. (165kB)
+ [SUCCESSFUL ] apache/commons-lang-2.0/commons-lang.jar[jar] (8032ms)
+downloading http://www.ibiblio.org/maven/commons-httpclient/jars/commons-httpclient-2.0.2.jar(2.0.2) ...
+...........
+......
+....
+..........
+............
+........ (220kB)
+ [SUCCESSFUL ] apache/commons-httpclient-2.0.2/commons-httpclient.jar[jar] (10031ms)
+downloading http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.0.4.jar(1.0.4) ...
+......... (37kB)
+ [SUCCESSFUL ] apache/commons-logging-1.0.4/commons-logging.jar[jar] (1469ms)
+:: resolution report ::
+ ---------------------------------------------------------------------
+ | | modules || artifacts |
+ | conf | number| search|dwnlded|evicted|| number|dwnlded|
+ ---------------------------------------------------------------------
+ | default | 3 | 3 | 1 | 0 || 3 | 3 |
+ ---------------------------------------------------------------------
+:: retrieving :: jayasoft/hello-ivy
+ confs: [default]
+ 3 artifacts copied, 0 already retrieved
+
+run:
+ [mkdir] Created dir: I:\dual\project\build
+ [javac] Compiling 1 source file to I:\dual\project\build
+ [java] standard message : hello ivy !
+ [java] capitalized by org.apache.commons.lang.WordUtils : Hello Ivy !
+ [java] head status code with httpclient: 200
+ [java] now check if httpclient dependency on commons-logging has been realized
+ [java] found logging class in classpath: interface org.apache.commons.logging.Log
+
+BUILD SUCCESSFUL
+Total time: 24 seconds
+</pre></div></div>
+<br/>
+As you can see, ivy not only downloaded commons-lang and commons-httpclient, but also commons-logging. Indeed, commons-logging is a dependency of httpclient, as we can see in the httpclient ivy file found in the repository directory:
+<code>
+<ivy-module version="1.0">
+ <info organisation="apache" module="commons-httpclient" revision="2.0.2" status="release" publication="20041010174300" />
+ <dependencies>
+ <dependency name="commons-logging" rev="1.0.4" conf="default" />
+ </dependencies>
+</ivy-module>
+</code>
+<br/>
+So everything worked well, ivy file has been found in the repository directory and artifacts have been downloaded from ibiblio. You now just have to write ivy files for the module you often use, and they will be much easier to use... And imagine a world in which each module delivers also an ivy file. Since it is independent of the way to retrieve dependencies, it would made all dependencies handling much easier, wouldn't it?
+
+
</textarea>
<script type="text/javascript">xooki.postProcess();</script>
</body>
Modified: incubator/ivy/core/trunk/doc/doc/tutorial/ivyrep.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/tutorial/ivyrep.html?view=diff&rev=519939&r1=519938&r2=519939
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/tutorial/ivyrep.html (original)
+++ incubator/ivy/core/trunk/doc/doc/tutorial/ivyrep.html Mon Mar 19 06:14:32 2007
@@ -5,121 +5,121 @@
<script type="text/javascript" src="../../xooki/xooki.js"></script>
</head>
<body>
- <textarea id="xooki-source">
-In this example, we will see the easiest way to use ivy and benefit from its transitive dependencies feature.
-No configuration or other complicated files to write, only the list of libraries the project will use.
-
-<h1>The ivy.xml file</h1>
-This file is used to describe, the dependencies of the project on other libraries.
-Here is the sample :
-<code>
-<ivy-module version="1.0">
- <info organisation="jayasoft" module="hello-ivy" />
- <dependencies>
- <dependency org="apache" name="commons-lang" rev="2.0" />
- <dependency org="apache" name="commons-cli" rev="1.0" />
- </dependencies>
-</ivy-module>
-</code>
-The build file corresponding to use it, contains only :
-<code>
-<project xmlns:ivy="antlib:fr.jayasoft.ivy.ant" name="hello-ivy" default="run">
-
- ...
-
- <!-- =================================
- target: resolve
- ================================= -->
- <target name="resolve" description="--> retreive dependencies with ivy">
- <ivy:retrieve />
- </target>
-</project>
-</code>
-<h1>Running the project</h1>
-To run the sample, open a shell window, and go under the ivyrep example directory.
-Then, on the command prompt, just run ant :
-<div class="shell"><pre>
-I:\ivyrep>ant
-Buildfile: build.xml
-
-resolve:
-:: Ivy 1.0-rc3 - 20050421161206 :: http://ivy.jayasoft.org/ ::
-no configuration file found, using default...
-:: resolving dependencies :: jayasoft/ivyrep-example-working@xmen
- confs: [default]
-downloading http://www.ibiblio.org/maven/commons-cli/jars/commons-cli-1.0.jar(1.0) ...
-...... (31kB)
- [SUCCESSFUL ] apache/commons-cli-1.0/commons-cli.jar[jar] (1437ms)
-downloading http://www.ibiblio.org/maven/commons-lang/jars/commons-lang-2.0.jar(2.0) ...
-..................................... (165kB)
- [SUCCESSFUL ] apache/commons-lang-2.0/commons-lang.jar[jar] (5640ms)
-downloading http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.0.jar(1.0) ...
-..... (21kB)
- [SUCCESSFUL ] apache/commons-logging-1.0/commons-logging.jar[jar] (1250ms)
-:: resolution report ::
- :: evicted modules:
- apache/commons-lang-1.0 by [apache/commons-lang-2.0] in [default]
- ---------------------------------------------------------------------
- | | modules || artifacts |
- | conf | number| search|dwnlded|evicted|| number|dwnlded|
- ---------------------------------------------------------------------
- | default | 4 | 3 | 2 | 1 || 3 | 3 |
- ---------------------------------------------------------------------
-:: retrieving :: jayasoft/ivyrep-example
- confs: [default]
- 3 artifacts copied, 0 already retrieved
-
-run:
- [mkdir] Created dir: I:\ivyrep\build
- [javac] Compiling 1 source file to I:\ivyrep\build
- [java] standard message : hello ivy !
- [java] capitalized by org.apache.commons.lang.WordUtils : Hello Ivy !
-
-BUILD SUCCESSFUL
-Total time: 16 seconds</pre></div>
-<h1>What happened ?</h1>
-Without any configuration, other than it's default configuration, ivy uses the ivyrep resolver. This resolver looks for ivy files on <a href="../../ivyrep.html">ivyrep</a>, and for artifacts on ibiblio. That's what happened here.
-
-The resolve task has found an <a href="http://ivyrep.jayasoft.org/apache/commons-cli/ivy-1.0.xml">ivy file on ivyrep for commons-cli 1.0</a>.
-This ivy file indicates that commons-cli 1.0 depends on commons-lang 1.0 and commons-logging 1.0.
-
-The resolve task detects the conflict between the revision 2.0 of commons-lang that is asked in the ivy above, and the revision 1.0 required in commons-cli. With no particular conflict manager, the 2.0 is selected, and the 1.0 is evicted. The 1.0 being evicted, it is not downloaded at all.
-
-The resolve task has then downloaded the commons-cli 1.0, commons-logging 1.0 and commons-lang.jar 2.0 files from ibiblioand put them to the ivy cache.
-Then the retrieve task has copied them in the default library directory of the project: the lib dir.
-Some will say that the task was long to achieve. Yes, it's true it was, but it has downloaded from the internet the needed files. Let's try to run it again:
-<div class="shell"><pre>
-I:\ivyrep>ant
-Buildfile: build.xml
-
-resolve:
-:: Ivy 1.0-rc3 - 20050421161206 :: http://ivy.jayasoft.org/ ::
-no configuration file found, using default...
-:: resolving dependencies :: jayasoft/ivyrep-example-working@xmen
- confs: [default]
-:: resolution report ::
- :: evicted modules:
- apache/commons-lang-1.0 by [apache/commons-lang-2.0] in [default]
- ---------------------------------------------------------------------
- | | modules || artifacts |
- | conf | number| search|dwnlded|evicted|| number|dwnlded|
- ---------------------------------------------------------------------
- | default | 4 | 0 | 0 | 1 || 3 | 0 |
- ---------------------------------------------------------------------
-:: retrieving :: jayasoft/ivyrep-example
- confs: [default]
- 0 artifacts copied, 3 already retrieved
-
-run:
- [java] standard message : hello ivy !
- [java] capitalized by org.apache.commons.lang.WordUtils : Hello Ivy !
-
-BUILD SUCCESSFUL
-Total time: 2 seconds</pre></div>
-Great ! the cache was used, no download was needed and the build was almost instantaneous.
-
-If you want to check the content of the cache, by default it is put in your user home in a .ivy/cache directory. Check the next tutorials to see how to configure this.
-
+ <textarea id="xooki-source">
+In this example, we will see the easiest way to use ivy and benefit from its transitive dependencies feature.
+No settings or other complicated files to write, only the list of libraries the project will use.
+
+<h1>The ivy.xml file</h1>
+This file is used to describe, the dependencies of the project on other libraries.
+Here is the sample :
+<code>
+<ivy-module version="1.0">
+ <info organisation="jayasoft" module="hello-ivy" />
+ <dependencies>
+ <dependency org="apache" name="commons-lang" rev="2.0" />
+ <dependency org="apache" name="commons-cli" rev="1.0" />
+ </dependencies>
+</ivy-module>
+</code>
+The build file corresponding to use it, contains only :
+<code>
+<project xmlns:ivy="antlib:fr.jayasoft.ivy.ant" name="hello-ivy" default="run">
+
+ ...
+
+ <!-- =================================
+ target: resolve
+ ================================= -->
+ <target name="resolve" description="--> retreive dependencies with ivy">
+ <ivy:retrieve />
+ </target>
+</project>
+</code>
+<h1>Running the project</h1>
+To run the sample, open a shell window, and go under the ivyrep example directory.
+Then, on the command prompt, just run ant :
+<div class="shell"><pre>
+I:\ivyrep>ant
+Buildfile: build.xml
+
+resolve:
+:: Ivy 1.0-rc3 - 20050421161206 :: http://ivy.jayasoft.org/ ::
+no configuration file found, using default...
+:: resolving dependencies :: jayasoft/ivyrep-example-working@xmen
+ confs: [default]
+downloading http://www.ibiblio.org/maven/commons-cli/jars/commons-cli-1.0.jar(1.0) ...
+...... (31kB)
+ [SUCCESSFUL ] apache/commons-cli-1.0/commons-cli.jar[jar] (1437ms)
+downloading http://www.ibiblio.org/maven/commons-lang/jars/commons-lang-2.0.jar(2.0) ...
+..................................... (165kB)
+ [SUCCESSFUL ] apache/commons-lang-2.0/commons-lang.jar[jar] (5640ms)
+downloading http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.0.jar(1.0) ...
+..... (21kB)
+ [SUCCESSFUL ] apache/commons-logging-1.0/commons-logging.jar[jar] (1250ms)
+:: resolution report ::
+ :: evicted modules:
+ apache/commons-lang-1.0 by [apache/commons-lang-2.0] in [default]
+ ---------------------------------------------------------------------
+ | | modules || artifacts |
+ | conf | number| search|dwnlded|evicted|| number|dwnlded|
+ ---------------------------------------------------------------------
+ | default | 4 | 3 | 2 | 1 || 3 | 3 |
+ ---------------------------------------------------------------------
+:: retrieving :: jayasoft/ivyrep-example
+ confs: [default]
+ 3 artifacts copied, 0 already retrieved
+
+run:
+ [mkdir] Created dir: I:\ivyrep\build
+ [javac] Compiling 1 source file to I:\ivyrep\build
+ [java] standard message : hello ivy !
+ [java] capitalized by org.apache.commons.lang.WordUtils : Hello Ivy !
+
+BUILD SUCCESSFUL
+Total time: 16 seconds</pre></div>
+<h1>What happened ?</h1>
+Without any settings, other than it's default settings, ivy uses the ivyrep resolver. This resolver looks for ivy files on <a href="../../ivyrep.html">ivyrep</a>, and for artifacts on ibiblio. That's what happened here.
+
+The resolve task has found an <a href="http://ivyrep.jayasoft.org/apache/commons-cli/ivy-1.0.xml">ivy file on ivyrep for commons-cli 1.0</a>.
+This ivy file indicates that commons-cli 1.0 depends on commons-lang 1.0 and commons-logging 1.0.
+
+The resolve task detects the conflict between the revision 2.0 of commons-lang that is asked in the ivy above, and the revision 1.0 required in commons-cli. With no particular conflict manager, the 2.0 is selected, and the 1.0 is evicted. The 1.0 being evicted, it is not downloaded at all.
+
+The resolve task has then downloaded the commons-cli 1.0, commons-logging 1.0 and commons-lang.jar 2.0 files from ibiblioand put them to the ivy cache.
+Then the retrieve task has copied them in the default library directory of the project: the lib dir.
+Some will say that the task was long to achieve. Yes, it's true it was, but it has downloaded from the internet the needed files. Let's try to run it again:
+<div class="shell"><pre>
+I:\ivyrep>ant
+Buildfile: build.xml
+
+resolve:
+:: Ivy 1.0-rc3 - 20050421161206 :: http://ivy.jayasoft.org/ ::
+no configuration file found, using default...
+:: resolving dependencies :: jayasoft/ivyrep-example-working@xmen
+ confs: [default]
+:: resolution report ::
+ :: evicted modules:
+ apache/commons-lang-1.0 by [apache/commons-lang-2.0] in [default]
+ ---------------------------------------------------------------------
+ | | modules || artifacts |
+ | conf | number| search|dwnlded|evicted|| number|dwnlded|
+ ---------------------------------------------------------------------
+ | default | 4 | 0 | 0 | 1 || 3 | 0 |
+ ---------------------------------------------------------------------
+:: retrieving :: jayasoft/ivyrep-example
+ confs: [default]
+ 0 artifacts copied, 3 already retrieved
+
+run:
+ [java] standard message : hello ivy !
+ [java] capitalized by org.apache.commons.lang.WordUtils : Hello Ivy !
+
+BUILD SUCCESSFUL
+Total time: 2 seconds</pre></div>
+Great ! the cache was used, no download was needed and the build was almost instantaneous.
+
+If you want to check the content of the cache, by default it is put in your user home in a .ivy/cache directory. Check the next tutorials to see how to configure this.
+
</textarea>
<script type="text/javascript">xooki.postProcess();</script>
</body>
Modified: incubator/ivy/core/trunk/doc/doc/tutorial/multi-project.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/tutorial/multi-project.html?view=diff&rev=519939&r1=519938&r2=519939
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/tutorial/multi-project.html (original)
+++ incubator/ivy/core/trunk/doc/doc/tutorial/multi-project.html Mon Mar 19 06:14:32 2007
@@ -5,314 +5,314 @@
<script type="text/javascript" src="../../xooki/xooki.js"></script>
</head>
<body>
- <textarea id="xooki-source">
-This example is an illustration of dependency between two project.
-
-The dependant project declares that it uses the standalone one. We will illustrate two things :
-<ul>
- <li>public libraries declared by standalone project will automatically be recovered by the dependant project</li>
- <li>the dependant project will retrieve the "latest" version of the standalone project</li>
-</ul>
-<h1>the projects used</h1>
-<h2>the project : standalone</h2>
-The standalone project is very simple. It depends on the apache library commons-lang and contains only one class: standalone.Main which provides two services:
-<ul>
- <li>return the version of the project</li>
- <li>capitalize a string using org.apache.commons.lang.WordUtils.capitalizeFully</li>
-</ul>
-Here is the content of the project:
-<ul>
- <li>build.xml : the ant build file for the project</li>
- <li>ivy.xml : the ivy project file</li>
- <li>src\standalone\Main.java : the only class of the project</li>
-</ul>
-Take a look at it's <b>ivy.xml</b> file:
-<code>
-<ivy-module version="1.0">
- <info organisation="jayasoft" module="standalone" />
- <dependencies>
- <dependency org="apache" name="commons-lang" rev="2.0" />
- </dependencies>
-</ivy-module>
-</code>
-
-The ivy dependency file declares only one dependency on apache commons-lang library which by default is a public dependency (see <a href="../../doc/ivyfile.html">ivy file definition</a>).
-<h2>the project : depending</h2>
-The project depending is very simple too. It declares only one dependency on the latest version of the standalone project and it contains only one class depending.Main which make 2 things:
-<ul>
- <li>getting the version of the standalone project throw a call to standalone.Main.getVersion()</li>
- <li>transform a string throw a call to standalone.Main.capitalizeWords(str)</li>
-</ul>
-Take a look at it's <b>ivy.xml</b> file:
-<code>
-<ivy-module version="1.0">
- <info organisation="jayasoft" module="depending" />
- <dependencies>
- <dependency name="standalone" rev="latest.integration" />
- </dependencies>
-</ivy-module>
-</code>
-
-<h2>the <b>ivy</b> configuration</h2>
-The ivy configuration is made in the config directory wich contains 2 files :
-<ul>
- <li>ivysettings.properties : a property file</li>
- <li>ivysettings.xml : the file containing the ivy configuration</li>
-</ul>
-
-Let's analyse the ivysettings.xml file.
-<code>
-<ivysettings>
- <properties file="${ivy.settings.dir}/ivysettings.properties" />
- <conf defaultCache="${ivy.settings.dir}/ivy-cache" defaultResolver="libraries" />
- <resolvers>
- <filesystem name="projects">
- <artifact pattern="${repository.dir}/[artifact]-[revision].[ext]" />
- <ivy pattern="${repository.dir}/[module]-[revision].xml" />
- </filesystem>
- <ivyrep name="libraries" />
- </resolvers>
- <modules>
- <module organisation="jayasoft" name=".*" resolver="projects" />
- </modules>
-</ivysettings>
-</code>
-The file contains four main tags : properties, conf, resolvers and modules.
-<h2>the <b>properties</b> tag</h2>
-This tag only load some properties for the ivy process in the same manner as ant will do it.
-<h2>the <b>conf</b> tag</h2>
-This tag is in charge to initialize some parameters for ivy process. The directory that ivy will use to cache (to store) artifacts found will be in a sub directory called ivy-cache of the directory containing the ivysettings.xml file itself.
-The second parameter, tells ivy to use a resolver called "libraries" as its default resolver. As a recall, a resolver is in charge to resolve an artifact from some information like : the organisation that provides the artifact, the name of the library and the version of the library. More information can be found in the <a href="../../doc/configuration.html">configuration documentation</a>.
-<h2>the <b>resolvers</b> tag</h2>
-This tag defines the resolvers to use. Here we have two resolvers defined: "projects" and "libraries".
-The filesystem resolver called "projects" is able to resolve the internal dependencies wanted.
-The ivyrep resolver called "libraries" is able to find dependencies on <a href="../../ivyrep.html">ivyrep</a>.
-<h2>the <b>modules</b> tag</h2>
-The modules tag allows to configure which resolver should be use for which module. Here the configuration only tells to use the "projects" resolver for all modules having for organisation "jayasoft" and any module name (.* regexp matches any module name).
-For other modules (i.e. all modules not from jayasoft), since there is no special configuration, the default resolver will be used: "libraries".
-<h1>walkthrough</h1>
-<div class="step">
-<h2>step 1 : preparation</h2>
-Open a DOS or shell window, and go to the "dependance" directory.
-</div>
-<div class="step">
-<h2>step 2 : clean directory tree</h2>
-On the prompt type : ant
-This will clean up the entire project directory tree. You can do it each time you want to clean up this example.
-</div>
-<div class="step">
-<h2>step 3 : publication of standalone project</h2>
-Goto standalone directory and publish the project
-<div class="shell"><pre>I:\standalone>ant publish
-Buildfile: build.xml
-
-configure:
-:: Ivy 1.0-rc3 - 20050421161206 :: http://ivy.jayasoft.org/ ::
-
-resolve:
-:: resolving dependencies :: jayasoft/standalone-working@xmen
- confs: [default]
-downloading http://www.ibiblio.org/maven/commons-lang/jars/commons-lang-2.0.jar(2.0) ...
-.................................... (165kB)
- [SUCCESSFUL ] apache/commons-lang-2.0/commons-lang.jar[jar] (6672ms)
-:: resolution report ::
- ---------------------------------------------------------------------
- | | modules || artifacts |
- | conf | number| search|dwnlded|evicted|| number|dwnlded|
- ---------------------------------------------------------------------
- | default | 1 | 1 | 0 | 0 || 1 | 1 |
- ---------------------------------------------------------------------
-:: retrieving :: jayasoft/standalone
- confs: [default]
- 1 artifacts copied, 0 already retrieved
-
-compile:
- [mkdir] Created dir: I:\standalone\build\classes
- [javac] Compiling 1 source file to I:\standalone\build\classes
-
-jar:
-[propertyfile] Creating new property file: I:\standalone\build\classes\version.properties
- [jar] Building jar: I:\standalone\build\standalone.jar
-
-publish:
-:: delivering :: jayasoft/standalone-working@xmen :: 1 :: release :: Wed Apr 27 08:41:47 CEST 2005
- delivering ivy file to I:\standalone/build/ivy.xml
-:: publishing :: jayasoft/standalone-working@xmen
- published standalone to I:\config\repository\standalone-1.jar
- published ivy to I:\config\repository\standalone-1.xml
- [echo] project standalone released with version 1
-
-BUILD SUCCESSFUL
-Total time: 10 seconds</pre></div>
-What we see here:
-<ul>
- <li>the project depends on 1 library (1 artifact)</li>
- <li>the library was not in the ivy cahe and so was downloaded (1 downloaded)</li>
- <li>the project has been released under version number 1</li>
-</ul>
-</div>
-To give more details on the publish, as you can see the call to the publish task has resulted in two main things:
-- the delivery of a resolved ivy file to build/ivy.xml. This has been done because by default the publish task not only publishes artifacts but also ivy file. So it has looked to the path where the ivy file to publish should be, using the artifactspattern: ${build.dir}/[artifact].[ext].
-For an ivy file, this resolves to build/ivy.xml. Because this file does not exist, it automatically make a call to the deliver task which delivers a resolved ivy file to this destination.
-- the publication of artifact standalone and resolved ivy file to the repository. Both are mere copy of files found in the current project, more precisely in the build dir. This is because the artifactspattern has been set to ${build.dir}/[artifact].[ext], so standalone artifact is found in build/standalone.jar and ivy file in build/ivy.xml. And because we have asked the publish task to publish them using the "projects" resolver, these files are copied to repository\standalone-1.jar and to repository\standalone-1.xml, respecting the artifact and ivy patterns of our configuration (see above).
-
-<div class="step">
-<h2>step 4 : running the depending project</h2>
-Goto to directory depending and run ant
-<div class="shell"><pre>I:\depending>ant
-Buildfile: build.xml
-
-clean:
-
-configure:
-:: Ivy 1.0-rc3 - 20050421161206 :: http://ivy.jayasoft.org/ ::
-
-resolve:
-:: resolving dependencies :: jayasoft/depending-working@xmen
- confs: [default]
- [1] jayasoft/standalone
-downloading file:/I:/config/repository/standalone-1.jar(1) ...
-. (1kB)
- [SUCCESSFUL ] jayasoft/standalone-1/standalone.jar[jar] (15ms)
-:: resolution report ::
- ---------------------------------------------------------------------
- | | modules || artifacts |
- | conf | number| search|dwnlded|evicted|| number|dwnlded|
- ---------------------------------------------------------------------
- | default | 2 | 2 | 2 | 0 || 2 | 1 |
- ---------------------------------------------------------------------
-:: retrieving :: jayasoft/depending
- confs: [default]
- 2 artifacts copied, 0 already retrieved
-
-compile:
- [mkdir] Created dir: I:\depending\build\classes
- [javac] Compiling 1 source file to I:\depending\build\classes
-
-run:
- [java] you are using version 1 of class standalone.Main
- [java] standard message : i am depending.Main and standalone.Main will do the job for me
- [java] [standalone.Main] capitalizing string "i am depending.Main and standalone.Main will do the job for me"
- using org.apache.commons.lang.WordUtils
- [java] capitalized message : I Am Depending.main And Standalone.main Will Do The Job For Me
-
-BUILD SUCCESSFUL
-Total time: 3 seconds</pre></div>
-What we see here :
-<ul>
- <li>the project depends on 2 libraries (2 artifacts)</li>
- <li>one of the libraries was in the cache because there was only 1 download (1 downloaded)</li>
- <li>ivy retreived the version 1 of the project standalone. The call to standalone.Main.getVersion() has returned 1. If you look in the depending/lib directory, you should see standalone-1.jar which is the artifact version 1 of the project standalone</li>
- <li>the call to standalone.Main.capitalizeWords(str) succeed, what significate that the required library were in the classpath. If you look at the lib directory, you will see that the library commons-lang-2.0.jar was retreived. This library was declared to be used by the project "standalone", so ivy get it too for the dependant project.</li>
-</ul>
-</div>
-<div class="step">
-<h2>step 5 : new version of standalone project</h2>
-Like we did before in step 3, publish again the standalone project. This will result as a new version of the project.
-<div class="shell"><pre>I:\standalone>ant publish
-Buildfile: build.xml
-
-configure:
-:: Ivy 1.0-rc3 - 20050421161206 :: http://ivy.jayasoft.org/ ::
-
-resolve:
-:: resolving dependencies :: jayasoft/standalone-working@xmen
- confs: [default]
-:: resolution report ::
- ---------------------------------------------------------------------
- | | modules || artifacts |
- | conf | number| search|dwnlded|evicted|| number|dwnlded|
- ---------------------------------------------------------------------
- | default | 1 | 0 | 0 | 0 || 1 | 0 |
- ---------------------------------------------------------------------
-:: retrieving :: jayasoft/standalone
- confs: [default]
- 0 artifacts copied, 1 already retrieved
-
-compile:
-
-jar:
-[propertyfile] Updating property file: I:\standalone\build\classes\version.properties
- [jar] Building jar: I:\standalone\build\standalone.jar
-
-publish:
- [delete] Deleting: I:\standalone\build\ivy.xml
-:: delivering :: jayasoft/standalone-working@xmen :: 2 :: release :: Wed Apr 27 09:17:13 CEST 2005
- delivering ivy file to I:\standalone/build/ivy.xml
-:: publishing :: jayasoft/standalone-working@xmen
- published standalone to I:\config\repository\standalone-2.jar
- published ivy to I:\config\repository\standalone-2.xml
- [echo] project standalone released with version 2
-
-BUILD SUCCESSFUL
-Total time: 2 seconds</pre></div>
-Now if you look in your repository folder, you must find 2 version published of the standalone project.
-Let's look at it:
-<div class="shell"><pre>I:\dependence\standalone>dir ..\config\repository /w
- Le volume dans le lecteur I s'appelle DATA
- Le numéro de série du volume est 30E5-91BA
-
- Répertoire de I:\dependence\config\repository
-
-[.] [..] standalone-1.jar standalone-1.xml standalone-2.jar standalone-2.xml
- 4 fichier(s) 3 936 octets
- 2 Rép(s) 9 874 350 080 octets libres
-
-I:\dependence\standalone></pre></div>
-</div>
-Ok now our repository contains two versions of the project <b>standalone</b>, other projects can refer to both versions.
-<div class="step">
-<h2>step 6 : depending got the new version</h2>
-What do we expect about running again the depending project? Two major things are expected:
-<ul>
- <li>retrieve the version 2 as the latest.integration version of the standalone project</li>
- <li>running the test must display version 2 of standalone project</li>
-</ul>
-Let's go!!!
-<div class="shell"><pre>I:\depending>ant
-Buildfile: build.xml
-
-clean:
- [delete] Deleting 3 files from I:\depending
- [delete] Deleted 4 directories from I:\depending
-
-configure:
-:: Ivy 1.0-rc3 - 20050421161206 :: http://ivy.jayasoft.org/ ::
-
-resolve:
-:: resolving dependencies :: jayasoft/depending-working@xmen
- confs: [default]
- [2] jayasoft/standalone
-downloading file:/I:/config/repository/standalone-2.jar(2) ...
-. (1kB)
- [SUCCESSFUL ] jayasoft/standalone-2/standalone.jar[jar] (0ms)
-:: resolution report ::
- ---------------------------------------------------------------------
- | | modules || artifacts |
- | conf | number| search|dwnlded|evicted|| number|dwnlded|
- ---------------------------------------------------------------------
- | default | 2 | 2 | 2 | 0 || 2 | 1 |
- ---------------------------------------------------------------------
-:: retrieving :: jayasoft/depending
- confs: [default]
- 2 artifacts copied, 0 already retrieved
-
-compile:
- [mkdir] Created dir: I:\depending\build\classes
- [javac] Compiling 1 source file to I:\depending\build\classes
-
-run:
- [java] you are using version 2 of class standalone.Main
- [java] standard message : i am depending.Main and standalone.Main will do the job for me
- [java] [standalone.Main] capitalizing string "i am depending.Main and standalone.Main will do the job for me"
- using org.apache.commons.lang.WordUtils
- [java] capitalized message : I Am Depending.main And Standalone.main Will Do The Job For Me
-
-BUILD SUCCESSFUL
-Total time: 3 seconds</pre></div>
-Ok we have the result expected as the run target shows that we are using the version 2 of the main class of standalone project. If we take a look at the resolve target results, we can see that one artifact has been downloaded to the ivy cache. In fact this file is the version 2 of the standalone project that was taken from the repository, you can now retrieve it in the ivy-cache directory.
-</div>
-
+ <textarea id="xooki-source">
+This example is an illustration of dependency between two project.
+
+The dependant project declares that it uses the standalone one. We will illustrate two things :
+<ul>
+ <li>public libraries declared by standalone project will automatically be recovered by the dependant project</li>
+ <li>the dependant project will retrieve the "latest" version of the standalone project</li>
+</ul>
+<h1>the projects used</h1>
+<h2>the project : standalone</h2>
+The standalone project is very simple. It depends on the apache library commons-lang and contains only one class: standalone.Main which provides two services:
+<ul>
+ <li>return the version of the project</li>
+ <li>capitalize a string using org.apache.commons.lang.WordUtils.capitalizeFully</li>
+</ul>
+Here is the content of the project:
+<ul>
+ <li>build.xml : the ant build file for the project</li>
+ <li>ivy.xml : the ivy project file</li>
+ <li>src\standalone\Main.java : the only class of the project</li>
+</ul>
+Take a look at it's <b>ivy.xml</b> file:
+<code>
+<ivy-module version="1.0">
+ <info organisation="jayasoft" module="standalone" />
+ <dependencies>
+ <dependency org="apache" name="commons-lang" rev="2.0" />
+ </dependencies>
+</ivy-module>
+</code>
+
+The ivy dependency file declares only one dependency on apache commons-lang library which by default is a public dependency (see <a href="../../doc/ivyfile.html">ivy file definition</a>).
+<h2>the project : depending</h2>
+The project depending is very simple too. It declares only one dependency on the latest version of the standalone project and it contains only one class depending.Main which make 2 things:
+<ul>
+ <li>getting the version of the standalone project throw a call to standalone.Main.getVersion()</li>
+ <li>transform a string throw a call to standalone.Main.capitalizeWords(str)</li>
+</ul>
+Take a look at it's <b>ivy.xml</b> file:
+<code>
+<ivy-module version="1.0">
+ <info organisation="jayasoft" module="depending" />
+ <dependencies>
+ <dependency name="standalone" rev="latest.integration" />
+ </dependencies>
+</ivy-module>
+</code>
+
+<h2>the <b>ivy</b> settings</h2>
+The ivy settings is made in the config directory wich contains 2 files :
+<ul>
+ <li>ivysettings.properties : a property file</li>
+ <li>ivysettings.xml : the file containing the ivy settings</li>
+</ul>
+
+Let's analyse the ivysettings.xml file.
+<code>
+<ivysettings>
+ <properties file="${ivy.settings.dir}/ivysettings.properties" />
+ <settings defaultCache="${ivy.settings.dir}/ivy-cache" defaultResolver="libraries" />
+ <resolvers>
+ <filesystem name="projects">
+ <artifact pattern="${repository.dir}/[artifact]-[revision].[ext]" />
+ <ivy pattern="${repository.dir}/[module]-[revision].xml" />
+ </filesystem>
+ <ivyrep name="libraries" />
+ </resolvers>
+ <modules>
+ <module organisation="jayasoft" name=".*" resolver="projects" />
+ </modules>
+</ivysettings>
+</code>
+The file contains four main tags: properties, settings, resolvers and modules.
+<h2>the <b>properties</b> tag</h2>
+This tag only load some properties for the ivy process in the same manner as ant will do it.
+<h2>the <b>settings</b> tag</h2>
+This tag is in charge to initialize some parameters for ivy process. The directory that ivy will use to cache (to store) artifacts found will be in a sub directory called ivy-cache of the directory containing the ivysettings.xml file itself.
+The second parameter, tells ivy to use a resolver called "libraries" as its default resolver. As a recall, a resolver is in charge to resolve an artifact from some information like: the organisation that provides the artifact, the name of the library and the version of the library. More information can be found in the <a href="../../doc/configuration.html">settings documentation</a>.
+<h2>the <b>resolvers</b> tag</h2>
+This tag defines the resolvers to use. Here we have two resolvers defined: "projects" and "libraries".
+The filesystem resolver called "projects" is able to resolve the internal dependencies wanted.
+The ivyrep resolver called "libraries" is able to find dependencies on <a href="../../ivyrep.html">ivyrep</a>.
+<h2>the <b>modules</b> tag</h2>
+The modules tag allows to configure which resolver should be use for which module. Here the settings only tells to use the "projects" resolver for all modules having for organisation "jayasoft" and any module name (.* regexp matches any module name).
+For other modules (i.e. all modules not from jayasoft), since there is no special settings, the default resolver will be used: "libraries".
+<h1>walkthrough</h1>
+<div class="step">
+<h2>step 1: preparation</h2>
+Open a DOS or shell window, and go to the "dependance" directory.
+</div>
+<div class="step">
+<h2>step 2: clean directory tree</h2>
+On the prompt type : ant
+This will clean up the entire project directory tree. You can do it each time you want to clean up this example.
+</div>
+<div class="step">
+<h2>step 3: publication of standalone project</h2>
+Goto standalone directory and publish the project
+<div class="shell"><pre>I:\standalone>ant publish
+Buildfile: build.xml
+
+configure:
+:: Ivy 1.0-rc3 - 20050421161206 :: http://ivy.jayasoft.org/ ::
+
+resolve:
+:: resolving dependencies :: jayasoft/standalone-working@xmen
+ confs: [default]
+downloading http://www.ibiblio.org/maven/commons-lang/jars/commons-lang-2.0.jar(2.0) ...
+.................................... (165kB)
+ [SUCCESSFUL ] apache/commons-lang-2.0/commons-lang.jar[jar] (6672ms)
+:: resolution report ::
+ ---------------------------------------------------------------------
+ | | modules || artifacts |
+ | conf | number| search|dwnlded|evicted|| number|dwnlded|
+ ---------------------------------------------------------------------
+ | default | 1 | 1 | 0 | 0 || 1 | 1 |
+ ---------------------------------------------------------------------
+:: retrieving :: jayasoft/standalone
+ confs: [default]
+ 1 artifacts copied, 0 already retrieved
+
+compile:
+ [mkdir] Created dir: I:\standalone\build\classes
+ [javac] Compiling 1 source file to I:\standalone\build\classes
+
+jar:
+[propertyfile] Creating new property file: I:\standalone\build\classes\version.properties
+ [jar] Building jar: I:\standalone\build\standalone.jar
+
+publish:
+:: delivering :: jayasoft/standalone-working@xmen :: 1 :: release :: Wed Apr 27 08:41:47 CEST 2005
+ delivering ivy file to I:\standalone/build/ivy.xml
+:: publishing :: jayasoft/standalone-working@xmen
+ published standalone to I:\config\repository\standalone-1.jar
+ published ivy to I:\config\repository\standalone-1.xml
+ [echo] project standalone released with version 1
+
+BUILD SUCCESSFUL
+Total time: 10 seconds</pre></div>
+What we see here:
+<ul>
+ <li>the project depends on 1 library (1 artifact)</li>
+ <li>the library was not in the ivy cache and so was downloaded (1 downloaded)</li>
+ <li>the project has been released under version number 1</li>
+</ul>
+</div>
+To give more details on the publish, as you can see the call to the publish task has resulted in two main things:
+- the delivery of a resolved ivy file to build/ivy.xml. This has been done because by default the publish task not only publishes artifacts but also ivy file. So it has looked to the path where the ivy file to publish should be, using the artifactspattern: ${build.dir}/[artifact].[ext].
+For an ivy file, this resolves to build/ivy.xml. Because this file does not exist, it automatically make a call to the deliver task which delivers a resolved ivy file to this destination.
+- the publication of artifact standalone and resolved ivy file to the repository. Both are mere copy of files found in the current project, more precisely in the build dir. This is because the artifactspattern has been set to ${build.dir}/[artifact].[ext], so standalone artifact is found in build/standalone.jar and ivy file in build/ivy.xml. And because we have asked the publish task to publish them using the "projects" resolver, these files are copied to repository\standalone-1.jar and to repository\standalone-1.xml, respecting the artifact and ivy patterns of our settings (see above).
+
+<div class="step">
+<h2>step 4: running the depending project</h2>
+Goto to directory depending and run ant
+<div class="shell"><pre>I:\depending>ant
+Buildfile: build.xml
+
+clean:
+
+configure:
+:: Ivy 1.0-rc3 - 20050421161206 :: http://ivy.jayasoft.org/ ::
+
+resolve:
+:: resolving dependencies :: jayasoft/depending-working@xmen
+ confs: [default]
+ [1] jayasoft/standalone
+downloading file:/I:/config/repository/standalone-1.jar(1) ...
+. (1kB)
+ [SUCCESSFUL ] jayasoft/standalone-1/standalone.jar[jar] (15ms)
+:: resolution report ::
+ ---------------------------------------------------------------------
+ | | modules || artifacts |
+ | conf | number| search|dwnlded|evicted|| number|dwnlded|
+ ---------------------------------------------------------------------
+ | default | 2 | 2 | 2 | 0 || 2 | 1 |
+ ---------------------------------------------------------------------
+:: retrieving :: jayasoft/depending
+ confs: [default]
+ 2 artifacts copied, 0 already retrieved
+
+compile:
+ [mkdir] Created dir: I:\depending\build\classes
+ [javac] Compiling 1 source file to I:\depending\build\classes
+
+run:
+ [java] you are using version 1 of class standalone.Main
+ [java] standard message : i am depending.Main and standalone.Main will do the job for me
+ [java] [standalone.Main] capitalizing string "i am depending.Main and standalone.Main will do the job for me"
+ using org.apache.commons.lang.WordUtils
+ [java] capitalized message : I Am Depending.main And Standalone.main Will Do The Job For Me
+
+BUILD SUCCESSFUL
+Total time: 3 seconds</pre></div>
+What we see here :
+<ul>
+ <li>the project depends on 2 libraries (2 artifacts)</li>
+ <li>one of the libraries was in the cache because there was only 1 download (1 downloaded)</li>
+ <li>ivy retrieved the version 1 of the project standalone. The call to standalone.Main.getVersion() has returned 1. If you look in the depending/lib directory, you should see standalone-1.jar which is the artifact version 1 of the project standalone</li>
+ <li>the call to standalone.Main.capitalizeWords(str) succeed, which means that the required library were in the classpath. If you look at the lib directory, you will see that the library commons-lang-2.0.jar was retrieved. This library was declared to be used by the project "standalone", so ivy get it too for the dependant project.</li>
+</ul>
+</div>
+<div class="step">
+<h2>step 5 : new version of standalone project</h2>
+Like we did before in step 3, publish again the standalone project. This will result as a new version of the project.
+<div class="shell"><pre>I:\standalone>ant publish
+Buildfile: build.xml
+
+configure:
+:: Ivy 1.0-rc3 - 20050421161206 :: http://ivy.jayasoft.org/ ::
+
+resolve:
+:: resolving dependencies :: jayasoft/standalone-working@xmen
+ confs: [default]
+:: resolution report ::
+ ---------------------------------------------------------------------
+ | | modules || artifacts |
+ | conf | number| search|dwnlded|evicted|| number|dwnlded|
+ ---------------------------------------------------------------------
+ | default | 1 | 0 | 0 | 0 || 1 | 0 |
+ ---------------------------------------------------------------------
+:: retrieving :: jayasoft/standalone
+ confs: [default]
+ 0 artifacts copied, 1 already retrieved
+
+compile:
+
+jar:
+[propertyfile] Updating property file: I:\standalone\build\classes\version.properties
+ [jar] Building jar: I:\standalone\build\standalone.jar
+
+publish:
+ [delete] Deleting: I:\standalone\build\ivy.xml
+:: delivering :: jayasoft/standalone-working@xmen :: 2 :: release :: Wed Apr 27 09:17:13 CEST 2005
+ delivering ivy file to I:\standalone/build/ivy.xml
+:: publishing :: jayasoft/standalone-working@xmen
+ published standalone to I:\config\repository\standalone-2.jar
+ published ivy to I:\config\repository\standalone-2.xml
+ [echo] project standalone released with version 2
+
+BUILD SUCCESSFUL
+Total time: 2 seconds</pre></div>
+Now if you look in your repository folder, you must find 2 version published of the standalone project.
+Let's look at it:
+<div class="shell"><pre>I:\dependence\standalone>dir ..\config\repository /w
+ Le volume dans le lecteur I s'appelle DATA
+ Le numéro de série du volume est 30E5-91BA
+
+ Répertoire de I:\dependence\config\repository
+
+[.] [..] standalone-1.jar standalone-1.xml standalone-2.jar standalone-2.xml
+ 4 fichier(s) 3 936 octets
+ 2 Rép(s) 9 874 350 080 octets libres
+
+I:\dependence\standalone></pre></div>
+</div>
+Ok now our repository contains two versions of the project <b>standalone</b>, other projects can refer to both versions.
+<div class="step">
+<h2>step 6 : depending got the new version</h2>
+What do we expect about running again the depending project? Two major things are expected:
+<ul>
+ <li>retrieve the version 2 as the latest.integration version of the standalone project</li>
+ <li>running the test must display version 2 of standalone project</li>
+</ul>
+Let's go!!!
+<div class="shell"><pre>I:\depending>ant
+Buildfile: build.xml
+
+clean:
+ [delete] Deleting 3 files from I:\depending
+ [delete] Deleted 4 directories from I:\depending
+
+configure:
+:: Ivy 1.0-rc3 - 20050421161206 :: http://ivy.jayasoft.org/ ::
+
+resolve:
+:: resolving dependencies :: jayasoft/depending-working@xmen
+ confs: [default]
+ [2] jayasoft/standalone
+downloading file:/I:/config/repository/standalone-2.jar(2) ...
+. (1kB)
+ [SUCCESSFUL ] jayasoft/standalone-2/standalone.jar[jar] (0ms)
+:: resolution report ::
+ ---------------------------------------------------------------------
+ | | modules || artifacts |
+ | conf | number| search|dwnlded|evicted|| number|dwnlded|
+ ---------------------------------------------------------------------
+ | default | 2 | 2 | 2 | 0 || 2 | 1 |
+ ---------------------------------------------------------------------
+:: retrieving :: jayasoft/depending
+ confs: [default]
+ 2 artifacts copied, 0 already retrieved
+
+compile:
+ [mkdir] Created dir: I:\depending\build\classes
+ [javac] Compiling 1 source file to I:\depending\build\classes
+
+run:
+ [java] you are using version 2 of class standalone.Main
+ [java] standard message : i am depending.Main and standalone.Main will do the job for me
+ [java] [standalone.Main] capitalizing string "i am depending.Main and standalone.Main will do the job for me"
+ using org.apache.commons.lang.WordUtils
+ [java] capitalized message : I Am Depending.main And Standalone.main Will Do The Job For Me
+
+BUILD SUCCESSFUL
+Total time: 3 seconds</pre></div>
+Ok we have the result expected as the run target shows that we are using the version 2 of the main class of standalone project. If we take a look at the resolve target results, we can see that one artifact has been downloaded to the ivy cache. In fact this file is the version 2 of the standalone project that was taken from the repository, you can now retrieve it in the ivy-cache directory.
+</div>
+
</textarea>
<script type="text/javascript">xooki.postProcess();</script>
</body>