incubator-ivy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From xav...@apache.org
Subject svn commit: r536488 [11/19] - in /incubator/ivy/core/trunk: ./ doc/ doc/doc/ doc/doc/configuration/ doc/doc/configuration/macrodef/ doc/doc/configuration/namespace/ doc/doc/ivyfile/ doc/doc/releasenotes/ doc/doc/resolver/ doc/doc/tutorial/ doc/doc/tuto...
Date Wed, 09 May 2007 10:58:16 GMT
Modified: incubator/ivy/core/trunk/doc/doc/resolver/ivyrep.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/resolver/ivyrep.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/resolver/ivyrep.html (original)
+++ incubator/ivy/core/trunk/doc/doc/resolver/ivyrep.html Wed May  9 03:58:10 2007
@@ -1,70 +1,70 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-<table class="resolver">
-<tr><td class="title">Tag</td><td class="value">ivyrep</td></tr>
-<tr><td class="title">Handle latest</td><td class="value">yes, at least if the repository server is apache based</td></tr>
-<tr><td class="title">Handle publish</td><td class="value">no</td></tr>
-</table>
-This resolver usually uses <a href="../../ivyrep.html">ivyrep</a> to find ivy files and ibiblio to find artifacts.
-However it can be configured to use other similar repositories.
-
-<i>Note that if no ivy file is found on ivyrep, then this resolver behaves like ibiblio resolver. Thus it's usually better to use this resolver instead of ibiblio one, which is provided mainly for compatibility reasons.</i>
-<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
-<table class="ivy-attributes">
-<thead>
-    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
-</thead>
-<tbody>
-    <tr><td>ivyroot</td><td>the root of the ivy repository.</td>
-        <td>No, defaults to ${ivy.ivyrep.default.ivy.root}</td></tr>
-    <tr><td>ivypattern</td><td>a pattern describing the layout of the ivy repository.</td>
-        <td>No, defaults to ${ivy.ivyrep.default.ivy.pattern}</td></tr>
-    <tr><td>artroot</td><td>the root of the artifacts repository.</td>
-        <td>No, defaults to ${ivy.ivyrep.default.artifact.root}</td></tr>
-    <tr><td>artpattern</td><td>a pattern describing the layout of the artifacts repository.</td>
-        <td>No, defaults to ${ivy.ivyrep.default.artifact pattern}</td></tr>
-</tbody>
-</table>
-<h1>Examples</h1>
-<code type="xml">
-<ivyrep name="ivyrep" />
-</code>
-A default ivyrep resolver, looking for ivy files on ivyrep and artifacts on ibiblio.
-
-<hr/>
-<code type="xml">
-<ivyrep name="ivyrep" ivyroot="http://ivyrep.mycompany.com"/>
-</code>
-Looks for ivy files on and ivyrep like web site located at http://ivyrep.mycompany.com.
-
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<table class="resolver">
+<tr><td class="title">Tag</td><td class="value">ivyrep</td></tr>
+<tr><td class="title">Handle latest</td><td class="value">yes, at least if the repository server is apache based</td></tr>
+<tr><td class="title">Handle publish</td><td class="value">no</td></tr>
+</table>
+This resolver usually uses <a href="../../ivyrep.html">ivyrep</a> to find ivy files and ibiblio to find artifacts.
+However it can be configured to use other similar repositories.
+
+<i>Note that if no ivy file is found on ivyrep, then this resolver behaves like ibiblio resolver. Thus it's usually better to use this resolver instead of ibiblio one, which is provided mainly for compatibility reasons.</i>
+<h1>Attributes</h1>
+This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>ivyroot</td><td>the root of the ivy repository.</td>
+        <td>No, defaults to ${ivy.ivyrep.default.ivy.root}</td></tr>
+    <tr><td>ivypattern</td><td>a pattern describing the layout of the ivy repository.</td>
+        <td>No, defaults to ${ivy.ivyrep.default.ivy.pattern}</td></tr>
+    <tr><td>artroot</td><td>the root of the artifacts repository.</td>
+        <td>No, defaults to ${ivy.ivyrep.default.artifact.root}</td></tr>
+    <tr><td>artpattern</td><td>a pattern describing the layout of the artifacts repository.</td>
+        <td>No, defaults to ${ivy.ivyrep.default.artifact pattern}</td></tr>
+</tbody>
+</table>
+<h1>Examples</h1>
+<code type="xml">
+<ivyrep name="ivyrep" />
+</code>
+A default ivyrep resolver, looking for ivy files on ivyrep and artifacts on ibiblio.
+
+<hr/>
+<code type="xml">
+<ivyrep name="ivyrep" ivyroot="http://ivyrep.mycompany.com"/>
+</code>
+Looks for ivy files on and ivyrep like web site located at http://ivyrep.mycompany.com.
+
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/resolver/ivyrep.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/resolver/sftp.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/resolver/sftp.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/resolver/sftp.html (original)
+++ incubator/ivy/core/trunk/doc/doc/resolver/sftp.html Wed May  9 03:58:10 2007
@@ -1,122 +1,122 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-<table class="resolver">
-<tr><td class="title">Tag</td><td class="value">sftp</td></tr>
-<tr><td class="title">Handle latest</td><td class="value">yes</td></tr>
-<tr><td class="title">Handle publish</td><td class="value">yes</td></tr>
-</table>
-
-<br/>
-This resolver can be used when your ivy repository is located on a server accessible via sftp. The secured nature of sftp and its wide spread implementation on most *nix servers makes this resolver a very good candidate in an enterprise environment. <span class="since">since 1.4</span>
-
-If your server supports ssh but not sftp, there is also an <a href="../../doc/resolver/ssh.html">ssh resolver</a>.
-
-Note that sftp is also supported by vfs, so you can use a vfs resolver instead. The advantage of this resolver is that you have a better control over authentication, it can prompt for username/password credentials, or you can use private/public key authentication, which is not possible with the vfs resolver. When it prompts for username/password, it uses a Swing dialog, which is not possible in a headless environment. If you want to prompt for the credentials on the command line, use ant input task for example before calling ivy.
-
-All necessary connection parameters can be set here via attributes.
-However all attributes defined in the pattern url of the resolver will have higher priority and will overwrite the values given here. To specify connection parameters in the pattern, you have to specify a full url and not just a path as pattern.
-e.g. pattern="/path/to/my/repos/[artifact].[ext]" will use all connection parameters from this class
-e.g. pattern="sftp://myserver.com/path/to/my/repos/[artifact].[ext]" will use all parameters from the attributes with the exception of the host, which will be "myserver.com"
-e.g. pattern="sftp://user:geheim@myserver.com:8022/path/to/my/repos/[artifact].[ext]" will use only the keyFile and keyFilePassword from the attributes (if needed). Rest will come from the url.
-
-
-Note that the authentication features of this resolver are exactly the same as the ssh resolver. Choosing between the two is often a matter of server implementation. If your server supports sftp, usually it's preferrable.
-
-Internally this resolver relies on <a href="http://www.jcraft.com/jsch/">jsch</a> as ssh client, which is a popular java ssh client, used for example in eclipse.
-
-<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
-<table class="ivy-attributes">
-<thead>
-    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
-</thead>
-<tbody>
-    <tr><td>user</td><td>The username to provide as credential</td>
-        <td>No, defaults to username given on the patterns, or prompt if none is set</td></tr>
-    <tr><td>userPassword</td><td>The password to provide as credential</td>
-        <td>No, defaults to password given on the patterns, or prompt if none is set</td></tr>
-    <tr><td>keyFile</td><td>Path to the keyfile to use for authentication</td>
-        <td>No, defaults to username/password authentication</td></tr>
-    <tr><td>keyFilePassword</td><td>the password used to protect the key file</td>
-        <td>No, will prompt for password if keyFile authentication is used and if it is password encrypted</td></tr>
-    <tr><td>host</td><td>The host to connect to</td>
-        <td>No, defaults to host given on the patterns, fail if none is set</td></tr>
-    <tr><td>port</td><td>The port to connect to</td>
-        <td>No, defaults to 22</td></tr>
-</tbody>
-</table>
-<h1>Child elements</h1>
-<table class="ivy-children">
-<thead>
-    <tr><th class="ivy-chld">Element</th><th class="ivy-chld-desc">Description</th><th class="ivy-chld-card">Cardinality</th></tr>
-</thead>
-<tbody>
-    <tr><td>ivy</td><td>defines a pattern for ivy files, using the pattern attribute</td>
-        <td>0..n</td></tr>
-    <tr><td>artifact</td><td>defines a pattern for artifacts, using the pattern attribute</td>
-        <td>1..n</td></tr>
-</tbody>
-</table>
-
-<h1>Example</h1>
-<code type="xml">
-<sftp user="myuser" host="myhost.com">
-  <ivy pattern="/path/to/ivy/[module]/ivy.xml"/>
-  <artifact pattern="/path/to/[organisation]/[module]/[artifact].[ext]"/>
-</sftp> 
-</code>
-Will connect to myhost.com using myuser and prompt for the password.
-<hr/>
-<code type="xml">
-<sftp user="${myuser}" userPassword="${my.password}" host="myhost.com">
-  <ivy pattern="path/to/ivy/[module]/ivy.xml"/>
-  <artifact pattern="path/to/[organisation]/[module]/[artifact].[ext]"/>
-</sftp>
-</code>
-Will connect to myhost.com using user and password provided with ivy variables.
-<hr/>
-<code type="xml">
-<sftp>
-  <ivy pattern="sftp://user:geheim@yourserver.com:8022/path/to/repos/[module]/[revision]/ivy.xml"/>
-  <artifact pattern="sftp://user:secret@myserver.com:8022/path/to/my/repos/[artifact].[ext]"/>
-</sftp>
-</code>
-Will connect to yourserver.com on port 8022 with user 'user' and password 'geheim' for authentication for ivy files, and to myserver.com on port 8022 using user 'user' and password 'secret' for the artifacts.
-<hr/>
-<code type="xml">
-<sftp keyFile="path/to/key/file" keyFilePassword="${password}">
-  <ivy pattern="sftp://user@yourserver.com:8022/path/to/repos/[module]/[revision]/ivy.xml"/>
-  <artifact pattern="sftp://user@myserver.com:8022/path/to/my/repos/[artifact].[ext]"/>
-</sftp>
-</code>
-Will connect to yourserver.com on port 8022 with user 'user' and use keyFile path/to/key/file for keyFile and the value of password variable for keyFilePassword authentication for ivy files, and to myserver.com on port 8022 using user 'user' with the same keyFile/keyFilePassword pair for the artifacts.
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<table class="resolver">
+<tr><td class="title">Tag</td><td class="value">sftp</td></tr>
+<tr><td class="title">Handle latest</td><td class="value">yes</td></tr>
+<tr><td class="title">Handle publish</td><td class="value">yes</td></tr>
+</table>
+
+<br/>
+This resolver can be used when your ivy repository is located on a server accessible via sftp. The secured nature of sftp and its wide spread implementation on most *nix servers makes this resolver a very good candidate in an enterprise environment. <span class="since">since 1.4</span>
+
+If your server supports ssh but not sftp, there is also an <a href="../../doc/resolver/ssh.html">ssh resolver</a>.
+
+Note that sftp is also supported by vfs, so you can use a vfs resolver instead. The advantage of this resolver is that you have a better control over authentication, it can prompt for username/password credentials, or you can use private/public key authentication, which is not possible with the vfs resolver. When it prompts for username/password, it uses a Swing dialog, which is not possible in a headless environment. If you want to prompt for the credentials on the command line, use ant input task for example before calling ivy.
+
+All necessary connection parameters can be set here via attributes.
+However all attributes defined in the pattern url of the resolver will have higher priority and will overwrite the values given here. To specify connection parameters in the pattern, you have to specify a full url and not just a path as pattern.
+e.g. pattern="/path/to/my/repos/[artifact].[ext]" will use all connection parameters from this class
+e.g. pattern="sftp://myserver.com/path/to/my/repos/[artifact].[ext]" will use all parameters from the attributes with the exception of the host, which will be "myserver.com"
+e.g. pattern="sftp://user:geheim@myserver.com:8022/path/to/my/repos/[artifact].[ext]" will use only the keyFile and keyFilePassword from the attributes (if needed). Rest will come from the url.
+
+
+Note that the authentication features of this resolver are exactly the same as the ssh resolver. Choosing between the two is often a matter of server implementation. If your server supports sftp, usually it's preferrable.
+
+Internally this resolver relies on <a href="http://www.jcraft.com/jsch/">jsch</a> as ssh client, which is a popular java ssh client, used for example in eclipse.
+
+<h1>Attributes</h1>
+This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>user</td><td>The username to provide as credential</td>
+        <td>No, defaults to username given on the patterns, or prompt if none is set</td></tr>
+    <tr><td>userPassword</td><td>The password to provide as credential</td>
+        <td>No, defaults to password given on the patterns, or prompt if none is set</td></tr>
+    <tr><td>keyFile</td><td>Path to the keyfile to use for authentication</td>
+        <td>No, defaults to username/password authentication</td></tr>
+    <tr><td>keyFilePassword</td><td>the password used to protect the key file</td>
+        <td>No, will prompt for password if keyFile authentication is used and if it is password encrypted</td></tr>
+    <tr><td>host</td><td>The host to connect to</td>
+        <td>No, defaults to host given on the patterns, fail if none is set</td></tr>
+    <tr><td>port</td><td>The port to connect to</td>
+        <td>No, defaults to 22</td></tr>
+</tbody>
+</table>
+<h1>Child elements</h1>
+<table class="ivy-children">
+<thead>
+    <tr><th class="ivy-chld">Element</th><th class="ivy-chld-desc">Description</th><th class="ivy-chld-card">Cardinality</th></tr>
+</thead>
+<tbody>
+    <tr><td>ivy</td><td>defines a pattern for ivy files, using the pattern attribute</td>
+        <td>0..n</td></tr>
+    <tr><td>artifact</td><td>defines a pattern for artifacts, using the pattern attribute</td>
+        <td>1..n</td></tr>
+</tbody>
+</table>
+
+<h1>Example</h1>
+<code type="xml">
+<sftp user="myuser" host="myhost.com">
+  <ivy pattern="/path/to/ivy/[module]/ivy.xml"/>
+  <artifact pattern="/path/to/[organisation]/[module]/[artifact].[ext]"/>
+</sftp> 
+</code>
+Will connect to myhost.com using myuser and prompt for the password.
+<hr/>
+<code type="xml">
+<sftp user="${myuser}" userPassword="${my.password}" host="myhost.com">
+  <ivy pattern="path/to/ivy/[module]/ivy.xml"/>
+  <artifact pattern="path/to/[organisation]/[module]/[artifact].[ext]"/>
+</sftp>
+</code>
+Will connect to myhost.com using user and password provided with ivy variables.
+<hr/>
+<code type="xml">
+<sftp>
+  <ivy pattern="sftp://user:geheim@yourserver.com:8022/path/to/repos/[module]/[revision]/ivy.xml"/>
+  <artifact pattern="sftp://user:secret@myserver.com:8022/path/to/my/repos/[artifact].[ext]"/>
+</sftp>
+</code>
+Will connect to yourserver.com on port 8022 with user 'user' and password 'geheim' for authentication for ivy files, and to myserver.com on port 8022 using user 'user' and password 'secret' for the artifacts.
+<hr/>
+<code type="xml">
+<sftp keyFile="path/to/key/file" keyFilePassword="${password}">
+  <ivy pattern="sftp://user@yourserver.com:8022/path/to/repos/[module]/[revision]/ivy.xml"/>
+  <artifact pattern="sftp://user@myserver.com:8022/path/to/my/repos/[artifact].[ext]"/>
+</sftp>
+</code>
+Will connect to yourserver.com on port 8022 with user 'user' and use keyFile path/to/key/file for keyFile and the value of password variable for keyFilePassword authentication for ivy files, and to myserver.com on port 8022 using user 'user' with the same keyFile/keyFilePassword pair for the artifacts.
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/resolver/sftp.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/resolver/ssh.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/resolver/ssh.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/resolver/ssh.html (original)
+++ incubator/ivy/core/trunk/doc/doc/resolver/ssh.html Wed May  9 03:58:10 2007
@@ -1,94 +1,94 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-<table class="resolver">
-<tr><td class="title">Tag</td><td class="value">ssh</td></tr>
-<tr><td class="title">Handle latest</td><td class="value">yes</td></tr>
-<tr><td class="title">Handle publish</td><td class="value">yes</td></tr>
-</table>
-
-<br/>
-This resolver can be used when your ivy repository is located on a server accessible via ssh. The secured nature of ssh and its wide spread implementation on most *nix servers makes this resolver a very good candidate in an enterprise environment. <span class="since">since 1.4</span>
-
-If your server supports sftp, you can consider using the <a href="../../doc/resolver/sftp.html">sftp resolver</a>.
-
-Internally this resolver shares most of its behaviour with the <a href="../../doc/resolver/sftp.html">sftp resolver</a>, so refer to its documentation for details.
-<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
-<table class="ivy-attributes">
-<thead>
-    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
-</thead>
-<tbody>
-    <tr><td>user</td><td>The username to provide as credential</td>
-        <td>No, defaults to username given on the patterns, or prompt if none is set</td></tr>
-    <tr><td>userPassword</td><td>The password to provide as credential</td>
-        <td>No, defaults to password given on the patterns, or prompt if none is set</td></tr>
-    <tr><td>keyFile</td><td>Path to the keyfile to use for authentication</td>
-        <td>No, defaults to username/password authentication</td></tr>
-    <tr><td>keyFilePassword</td><td>the password used to protect the key file</td>
-        <td>No, will prompt for password if keyFile authentication is used and if it is password encrypted</td></tr>
-    <tr><td>host</td><td>The host to connect to</td>
-        <td>No, defaults to host given on the patterns, fail if none is set</td></tr>
-    <tr><td>port</td><td>The port to connect to</td>
-        <td>No, defaults to 22</td></tr>
-</tbody>
-</table>
-<h1>Child elements</h1>
-<table class="ivy-children">
-<thead>
-    <tr><th class="ivy-chld">Element</th><th class="ivy-chld-desc">Description</th><th class="ivy-chld-card">Cardinality</th></tr>
-</thead>
-<tbody>
-    <tr><td>ivy</td><td>defines a pattern for ivy files, using the pattern attribute</td>
-        <td>0..n</td></tr>
-    <tr><td>artifact</td><td>defines a pattern for artifacts, using the pattern attribute</td>
-        <td>1..n</td></tr>
-</tbody>
-</table>
-
-<h1>Example</h1>
-<code type="xml">
-<ssh user="myuser" host="myhost.com">
-  <ivy pattern="/path/to/ivy/[module]/ivy.xml"/>
-  <artifact pattern="/path/to/[organisation]/[module]/[artifact].[ext]"/>
-</ssh> 
-</code>
-Will connect to myhost.com using myuser and prompt for the password.
-<hr/>
-<code type="xml">
-<ssh keyFile="path/to/key/file" keyFilePassword="${password}">
-  <ivy pattern="ssh://user:geheim@yourserver.com:8022/path/to/repos/[module]/[revision]/ivy.xml"/>
-  <artifact pattern="ssh://user:geheim@myserver.com:8022/path/to/my/repos/[artifact].[ext]"/>
-</ssh>
-</code>
-Will connect to yourserver.com on port 8022 with user geheim and use keyFile path/to/key/file for keyFile and the value of password variable for keyFilePassword authentication for ivy files, and to myserver.com on port 8022 using user geheim with the same keyFile/keyFilePassword pair for the artifacts.
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<table class="resolver">
+<tr><td class="title">Tag</td><td class="value">ssh</td></tr>
+<tr><td class="title">Handle latest</td><td class="value">yes</td></tr>
+<tr><td class="title">Handle publish</td><td class="value">yes</td></tr>
+</table>
+
+<br/>
+This resolver can be used when your ivy repository is located on a server accessible via ssh. The secured nature of ssh and its wide spread implementation on most *nix servers makes this resolver a very good candidate in an enterprise environment. <span class="since">since 1.4</span>
+
+If your server supports sftp, you can consider using the <a href="../../doc/resolver/sftp.html">sftp resolver</a>.
+
+Internally this resolver shares most of its behaviour with the <a href="../../doc/resolver/sftp.html">sftp resolver</a>, so refer to its documentation for details.
+<h1>Attributes</h1>
+This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>user</td><td>The username to provide as credential</td>
+        <td>No, defaults to username given on the patterns, or prompt if none is set</td></tr>
+    <tr><td>userPassword</td><td>The password to provide as credential</td>
+        <td>No, defaults to password given on the patterns, or prompt if none is set</td></tr>
+    <tr><td>keyFile</td><td>Path to the keyfile to use for authentication</td>
+        <td>No, defaults to username/password authentication</td></tr>
+    <tr><td>keyFilePassword</td><td>the password used to protect the key file</td>
+        <td>No, will prompt for password if keyFile authentication is used and if it is password encrypted</td></tr>
+    <tr><td>host</td><td>The host to connect to</td>
+        <td>No, defaults to host given on the patterns, fail if none is set</td></tr>
+    <tr><td>port</td><td>The port to connect to</td>
+        <td>No, defaults to 22</td></tr>
+</tbody>
+</table>
+<h1>Child elements</h1>
+<table class="ivy-children">
+<thead>
+    <tr><th class="ivy-chld">Element</th><th class="ivy-chld-desc">Description</th><th class="ivy-chld-card">Cardinality</th></tr>
+</thead>
+<tbody>
+    <tr><td>ivy</td><td>defines a pattern for ivy files, using the pattern attribute</td>
+        <td>0..n</td></tr>
+    <tr><td>artifact</td><td>defines a pattern for artifacts, using the pattern attribute</td>
+        <td>1..n</td></tr>
+</tbody>
+</table>
+
+<h1>Example</h1>
+<code type="xml">
+<ssh user="myuser" host="myhost.com">
+  <ivy pattern="/path/to/ivy/[module]/ivy.xml"/>
+  <artifact pattern="/path/to/[organisation]/[module]/[artifact].[ext]"/>
+</ssh> 
+</code>
+Will connect to myhost.com using myuser and prompt for the password.
+<hr/>
+<code type="xml">
+<ssh keyFile="path/to/key/file" keyFilePassword="${password}">
+  <ivy pattern="ssh://user:geheim@yourserver.com:8022/path/to/repos/[module]/[revision]/ivy.xml"/>
+  <artifact pattern="ssh://user:geheim@myserver.com:8022/path/to/my/repos/[artifact].[ext]"/>
+</ssh>
+</code>
+Will connect to yourserver.com on port 8022 with user geheim and use keyFile path/to/key/file for keyFile and the value of password variable for keyFilePassword authentication for ivy files, and to myserver.com on port 8022 using user geheim with the same keyFile/keyFilePassword pair for the artifacts.
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/resolver/ssh.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/resolver/url.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/resolver/url.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/resolver/url.html (original)
+++ incubator/ivy/core/trunk/doc/doc/resolver/url.html Wed May  9 03:58:10 2007
@@ -1,74 +1,74 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-<table class="resolver">
-<tr><td class="title">Tag</td><td class="value">url</td></tr>
-<tr><td class="title">Handle latest</td><td class="value">yes with http urls (and apache server) and with file urls, no with other urls</td></tr>
-<tr><td class="title">Handle publish</td><td class="value">no</td></tr>
-</table>
-
-<br/>
-This resolver is one of the most generic, in fact most of the previous resolvers can be obtained by a particular configuration of this one. Indeed it uses urls to find ivy files and artifacts. The urls it uses are defined through ivy and artifact children, each giving a pattern to find ivy files or artifacts.
-
-<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
-<table class="ivy-attributes">
-<thead>
-    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
-</thead>
-<tbody>
-    <tr><td>m2compatible</td><td>True if this resolver should be maven2 compatible, false otherwise <span class="since">since 1.3</span></td>
-        <td>No, defaults to false</td></tr>
-</tbody>
-</table>
-<h1>Child elements</h1>
-<table class="ivy-children">
-<thead>
-    <tr><th class="ivy-chld">Element</th><th class="ivy-chld-desc">Description</th><th class="ivy-chld-card">Cardinality</th></tr>
-</thead>
-<tbody>
-    <tr><td>ivy</td><td>defines a pattern for ivy files, using the pattern attribute</td>
-        <td>0..n</td></tr>
-    <tr><td>artifact</td><td>defines a pattern for artifacts, using the pattern attribute</td>
-        <td>1..n</td></tr>
-</tbody>
-</table>
-
-<h1>Example</h1>
-<code type="xml">
-<url name="two-patterns-example">
-  <ivy pattern="http://ivyrep.mycompany.com/[module]/[revision]/ivy-[revision].xml" />
-  <artifact pattern="http://ivyrep.mycompany.com/[module]/[revision]/[artifact]-[revision].[ext]" />
-  <artifact pattern="http://ivyrep.mycompany.com/[module]/[revision]/[artifact].[ext]" />
-</url>
-</code>
-Looks for ivy files in one place and for artifacts in two places: with or without revision in name (revision being already in the directory structure).
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<table class="resolver">
+<tr><td class="title">Tag</td><td class="value">url</td></tr>
+<tr><td class="title">Handle latest</td><td class="value">yes with http urls (and apache server) and with file urls, no with other urls</td></tr>
+<tr><td class="title">Handle publish</td><td class="value">no</td></tr>
+</table>
+
+<br/>
+This resolver is one of the most generic, in fact most of the previous resolvers can be obtained by a particular configuration of this one. Indeed it uses urls to find ivy files and artifacts. The urls it uses are defined through ivy and artifact children, each giving a pattern to find ivy files or artifacts.
+
+<h1>Attributes</h1>
+This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>m2compatible</td><td>True if this resolver should be maven2 compatible, false otherwise <span class="since">since 1.3</span></td>
+        <td>No, defaults to false</td></tr>
+</tbody>
+</table>
+<h1>Child elements</h1>
+<table class="ivy-children">
+<thead>
+    <tr><th class="ivy-chld">Element</th><th class="ivy-chld-desc">Description</th><th class="ivy-chld-card">Cardinality</th></tr>
+</thead>
+<tbody>
+    <tr><td>ivy</td><td>defines a pattern for ivy files, using the pattern attribute</td>
+        <td>0..n</td></tr>
+    <tr><td>artifact</td><td>defines a pattern for artifacts, using the pattern attribute</td>
+        <td>1..n</td></tr>
+</tbody>
+</table>
+
+<h1>Example</h1>
+<code type="xml">
+<url name="two-patterns-example">
+  <ivy pattern="http://ivyrep.mycompany.com/[module]/[revision]/ivy-[revision].xml" />
+  <artifact pattern="http://ivyrep.mycompany.com/[module]/[revision]/[artifact]-[revision].[ext]" />
+  <artifact pattern="http://ivyrep.mycompany.com/[module]/[revision]/[artifact].[ext]" />
+</url>
+</code>
+Looks for ivy files in one place and for artifacts in two places: with or without revision in name (revision being already in the directory structure).
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/resolver/url.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/resolver/vfs.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/resolver/vfs.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/resolver/vfs.html (original)
+++ incubator/ivy/core/trunk/doc/doc/resolver/vfs.html Wed May  9 03:58:10 2007
@@ -1,65 +1,65 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-<table class="resolver">
-<tr><td class="title">Tag</td><td class="value">vfs</td></tr>
-<tr><td class="title">Handle latest</td><td class="value">depend on vfs capacity, usually yes</td></tr>
-<tr><td class="title">Handle publish</td><td class="value">depend on vfs capacity, usually yes</td></tr>
-</table>
-<br/>
-This resolver is certainly the most capable, since it relies on <a href="http://jakarta.apache.org/commons/vfs/">Apache commons VFS</a>, which gives an uniform access to <a href="http://jakarta.apache.org/commons/vfs/filesystems.html">a good number of file systems</a>, including ftp, webdav, zip, ... <span class="since">since 1.4</span>
-
-<i>Note: commons vfs has not released a stable version yet, hence Ivy relies on a nightly build. Stability should thus be considered carefully before using this resolver in a production environment</i>
-
-<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
-<h1>Child elements</h1>
-<table class="ivy-children">
-<thead>
-    <tr><th class="ivy-chld">Element</th><th class="ivy-chld-desc">Description</th><th class="ivy-chld-card">Cardinality</th></tr>
-</thead>
-<tbody>
-    <tr><td>ivy</td><td>defines a pattern for ivy files, using the pattern attribute</td>
-        <td>0..n</td></tr>
-    <tr><td>artifact</td><td>defines a pattern for artifacts, using the pattern attribute</td>
-        <td>1..n</td></tr>
-</tbody>
-</table>
-
-<h1>Example</h1>
-<code type="xml">
-<vfs name="vfs-resolver">
-  <ivy pattern="sftp://username:password@host/[organisation]/[module]/[revision]/ivy.xml" />
-  <artifact pattern="sftp://username:password@host/[organisation]/[module]/[revision]/[artifact].[ext]" />
-</vfs> 
-</code>
-Access ivy and artifacts files using sftp.
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<table class="resolver">
+<tr><td class="title">Tag</td><td class="value">vfs</td></tr>
+<tr><td class="title">Handle latest</td><td class="value">depend on vfs capacity, usually yes</td></tr>
+<tr><td class="title">Handle publish</td><td class="value">depend on vfs capacity, usually yes</td></tr>
+</table>
+<br/>
+This resolver is certainly the most capable, since it relies on <a href="http://jakarta.apache.org/commons/vfs/">Apache commons VFS</a>, which gives an uniform access to <a href="http://jakarta.apache.org/commons/vfs/filesystems.html">a good number of file systems</a>, including ftp, webdav, zip, ... <span class="since">since 1.4</span>
+
+<i>Note: commons vfs has not released a stable version yet, hence Ivy relies on a nightly build. Stability should thus be considered carefully before using this resolver in a production environment</i>
+
+<h1>Attributes</h1>
+This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
+<h1>Child elements</h1>
+<table class="ivy-children">
+<thead>
+    <tr><th class="ivy-chld">Element</th><th class="ivy-chld-desc">Description</th><th class="ivy-chld-card">Cardinality</th></tr>
+</thead>
+<tbody>
+    <tr><td>ivy</td><td>defines a pattern for ivy files, using the pattern attribute</td>
+        <td>0..n</td></tr>
+    <tr><td>artifact</td><td>defines a pattern for artifacts, using the pattern attribute</td>
+        <td>1..n</td></tr>
+</tbody>
+</table>
+
+<h1>Example</h1>
+<code type="xml">
+<vfs name="vfs-resolver">
+  <ivy pattern="sftp://username:password@host/[organisation]/[module]/[revision]/ivy.xml" />
+  <artifact pattern="sftp://username:password@host/[organisation]/[module]/[revision]/[artifact].[ext]" />
+</vfs> 
+</code>
+Access ivy and artifacts files using sftp.
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/resolver/vfs.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/standalone.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/standalone.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/standalone.html (original)
+++ incubator/ivy/core/trunk/doc/doc/standalone.html Wed May  9 03:58:10 2007
@@ -1,94 +1,94 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 1};</script>	
-	<script type="text/javascript" src="../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-In the case you want to call ivy as a standalone program (outside from ant), you have to put commons-cli 1.0 and its dependencies in your classpath.
-
-Then here is how to call it:
-<code>
-java org.apache.ivy.Main -?
-</code>
-It will indicate you what can be given as argument. 
-
-
-<span class="since">since 1.3</span> System properties are included as ivy variables, so you can easily define an ivy variable like this:
-<code>
-java -Dmyivyvar=myvalue org.apache.ivy.Main [parameters]
-</code>
-
-
-<h1>Examples</h1>
-<code>
-java fr.jayasoft.ivy.Main
-</code>
-calls ivy with default configuration using ivy.xml in the current dir
-<hr/>
-<code>
-java fr.jayasoft.ivy.Main -conf path/to/myivysettings.xml -ivy path/to/myivy.xml
-</code>
-calls ivy with given ivysettings file using given ivy file
-<hr/>
-<span class="since">since 1.3</span>
-<code>
-java fr.jayasoft.ivy.Main -conf path/to/myivysettings.xml -dependency apache commons-lang 2.0
-</code>
-calls ivy with given ivysettings file and resolve apache commons-lang 2.0. 
-
-This is equivalent to:
-<code>
-java fr.jayasoft.ivy.Main -conf path/to/myivysettings.xml -ivy ivy.xml
-</code>
-with ivy.xml like this:
-<code type="xml">
-<ivy-module version="1.0">
-  <info organisation="org"
-       module="standalone"
-       revision="working"
-   />
-  <dependencies>
-    <dependency org="apache" name="commons-lang" rev="2.0" conf="default->*"/>
-  </dependencies>
-</ivy-module>
-</code>
-<hr/>
-<span class="since">since 1.3</span>
-<code>
-java fr.jayasoft.ivy.Main -conf path/to/myivysettings.xml -ivy path/to/myivy.xml -cachepath mycachefile.txt
-</code>
-calls ivy with given ivysettings file and resolve the dependencies found in the given ivy file, and then output the classpath of resolved artifacts in cache in a file. This file can then be used to define a classpath corresponding to all the resolved dependencies for any java program. 
-
-<hr/>
-<span class="since">since 1.4</span>
-<code>
-java fr.jayasoft.ivy.Main -conf path/to/myivysettings.xml -dependency bar foo 2.0 -main org.bar.foo.FooMain
-</code>
-calls ivy with given ivysettings file and resolve bar foo 2.0, and then run org.foo.FooMain class with the resolved artifacts as classpath
-
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+In the case you want to call ivy as a standalone program (outside from ant), you have to put commons-cli 1.0 and its dependencies in your classpath.
+
+Then here is how to call it:
+<code>
+java org.apache.ivy.Main -?
+</code>
+It will indicate you what can be given as argument. 
+
+
+<span class="since">since 1.3</span> System properties are included as ivy variables, so you can easily define an ivy variable like this:
+<code>
+java -Dmyivyvar=myvalue org.apache.ivy.Main [parameters]
+</code>
+
+
+<h1>Examples</h1>
+<code>
+java fr.jayasoft.ivy.Main
+</code>
+calls ivy with default configuration using ivy.xml in the current dir
+<hr/>
+<code>
+java fr.jayasoft.ivy.Main -conf path/to/myivysettings.xml -ivy path/to/myivy.xml
+</code>
+calls ivy with given ivysettings file using given ivy file
+<hr/>
+<span class="since">since 1.3</span>
+<code>
+java fr.jayasoft.ivy.Main -conf path/to/myivysettings.xml -dependency apache commons-lang 2.0
+</code>
+calls ivy with given ivysettings file and resolve apache commons-lang 2.0. 
+
+This is equivalent to:
+<code>
+java fr.jayasoft.ivy.Main -conf path/to/myivysettings.xml -ivy ivy.xml
+</code>
+with ivy.xml like this:
+<code type="xml">
+<ivy-module version="1.0">
+  <info organisation="org"
+       module="standalone"
+       revision="working"
+   />
+  <dependencies>
+    <dependency org="apache" name="commons-lang" rev="2.0" conf="default->*"/>
+  </dependencies>
+</ivy-module>
+</code>
+<hr/>
+<span class="since">since 1.3</span>
+<code>
+java fr.jayasoft.ivy.Main -conf path/to/myivysettings.xml -ivy path/to/myivy.xml -cachepath mycachefile.txt
+</code>
+calls ivy with given ivysettings file and resolve the dependencies found in the given ivy file, and then output the classpath of resolved artifacts in cache in a file. This file can then be used to define a classpath corresponding to all the resolved dependencies for any java program. 
+
+<hr/>
+<span class="since">since 1.4</span>
+<code>
+java fr.jayasoft.ivy.Main -conf path/to/myivysettings.xml -dependency bar foo 2.0 -main org.bar.foo.FooMain
+</code>
+calls ivy with given ivysettings file and resolve bar foo 2.0, and then run org.foo.FooMain class with the resolved artifacts as classpath
+
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/standalone.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/terminology.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/terminology.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/terminology.html (original)
+++ incubator/ivy/core/trunk/doc/doc/terminology.html Wed May  9 03:58:10 2007
@@ -1,81 +1,81 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 1};</script>	
-	<script type="text/javascript" src="../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-Here are some terms used in Ivy, with their definitions in Ivy:<br/>
-<h2>Ivy file</h2>
-An ivy file is an xml file which is used to describe dependencies of a module (see below). It is usually named ivy.xml.
-<h2>Settings</h2>
-Ivy settings files are xml files used to configure ivy to indicate where the dependencies can be found and how. 
-<em>Prior to Ivy 2.0, these files were called configuration files and usually named ivyconf.xml. This resulted in a confusion between module configurations and configuration files, so they have been renamed in settings files. 
-If you happen to fall on an ivyconf file or something called a configuration file, most of the time it's only a problem of update of the doc/tutorial/article. Feel free to report any problem like this if you find such inconsistencies in this documentation.</em>
-<h2>Organisation</h2>
-An organisation is either a company or a simple group of person
-which produce software. Ivy handle only one level of organisation, so you cannot
-describe a company hierarchy with this concept. But it is used to group sofware
-produced by a same team, just to help find and classify them.<br/>
-<i>Examples: apache, ibm, jayasoft</i>
-<h2>Module</h2>
-A module in ivy is a piece of software that is reusable, and that 
-follow a unique cycle of revision. <br/>
-<i>Examples: hibernate, ant, ...</i>
-<h2>Artifact</h2>
-An artifact is a single file produced by a company when releasing a module. In 
-the java world, common artifacts are jars. In many cases, each revision of a 
-module publish only one artifact (like log4j, for instance), but some of them
-publish many artifacts dependending on the use of the module (like ant, for instance).
-<h2>Revision</h2>
-A revision corresponds to one delivery of a module. It can either be a delivery
-of a release, a milestone, a beta version, a nightly build, or even a continuous
-build. All of them are considered revisions in ivy.
-<h2><a name="branch">Branch</a></h2>
-A branch corresponds to the standard meaning of a branch (or sometimes stream) in source control management tools.
-The head, or trunk, or main stream, is also considered as a branch in Ivy.
-<h2>Configuration</h2>
-A module configuration is a way to use or construct a module. Some modules may be used in different ways (think about hibernate which can be used inside or outside an application server), and this way may alter the artifacts you need (in the case of hibernate, jta.jar is needed only if it is used outside an application server).
-Moreover, a module may need some other modules and artifacts only at build time,
-and some others at runtime. All those differents ways to use or build a module
-are called in ivy configurations. 
-
-For more details on configurations and how they are used in ivy, please refer to the <a href="../doc/concept.html">main concepts page</a>.
-<h2>Status</h2>
-A module status indicates how stable a module revision can be considered. It can 
-be used to consolidate the status of all the dependencies of a module, to prevent
-the use of an integration revision of a dependency in the release of your module.
-Three statuses are defined by default in ivy:
-<ul>
-<li>integration: revisions builded by a continuous build, a nightly build, and so on, fall in this category</li>
-<li>milestone: revisions delivered to the public but not actually finished fall in this category</li>
-<li>release: revision fully tested and labelled fall in this category</li>
-</ul>
-<span class="since">since 1.4</span> This list is <a href="../doc/configuration/statuses.html">configurable</a> in your configuration file.
-<h2>Repository</h2>
-What is called a repository in Ivy is a location where Ivy is able to find your modules artifacts and metadata (i.e. ivy files in most cases).
-Ivy can be used with complex repositories configured very finely. You can use <a href="../doc/concept.html">Dependency Resolvers</a> to do so.
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Here are some terms used in Ivy, with their definitions in Ivy:<br/>
+<h2>Ivy file</h2>
+An ivy file is an xml file which is used to describe dependencies of a module (see below). It is usually named ivy.xml.
+<h2>Settings</h2>
+Ivy settings files are xml files used to configure ivy to indicate where the dependencies can be found and how. 
+<em>Prior to Ivy 2.0, these files were called configuration files and usually named ivyconf.xml. This resulted in a confusion between module configurations and configuration files, so they have been renamed in settings files. 
+If you happen to fall on an ivyconf file or something called a configuration file, most of the time it's only a problem of update of the doc/tutorial/article. Feel free to report any problem like this if you find such inconsistencies in this documentation.</em>
+<h2>Organisation</h2>
+An organisation is either a company or a simple group of person
+which produce software. Ivy handle only one level of organisation, so you cannot
+describe a company hierarchy with this concept. But it is used to group sofware
+produced by a same team, just to help find and classify them.<br/>
+<i>Examples: apache, ibm, jayasoft</i>
+<h2>Module</h2>
+A module in ivy is a piece of software that is reusable, and that 
+follow a unique cycle of revision. <br/>
+<i>Examples: hibernate, ant, ...</i>
+<h2>Artifact</h2>
+An artifact is a single file produced by a company when releasing a module. In 
+the java world, common artifacts are jars. In many cases, each revision of a 
+module publish only one artifact (like log4j, for instance), but some of them
+publish many artifacts dependending on the use of the module (like ant, for instance).
+<h2>Revision</h2>
+A revision corresponds to one delivery of a module. It can either be a delivery
+of a release, a milestone, a beta version, a nightly build, or even a continuous
+build. All of them are considered revisions in ivy.
+<h2><a name="branch">Branch</a></h2>
+A branch corresponds to the standard meaning of a branch (or sometimes stream) in source control management tools.
+The head, or trunk, or main stream, is also considered as a branch in Ivy.
+<h2>Configuration</h2>
+A module configuration is a way to use or construct a module. Some modules may be used in different ways (think about hibernate which can be used inside or outside an application server), and this way may alter the artifacts you need (in the case of hibernate, jta.jar is needed only if it is used outside an application server).
+Moreover, a module may need some other modules and artifacts only at build time,
+and some others at runtime. All those differents ways to use or build a module
+are called in ivy configurations. 
+
+For more details on configurations and how they are used in ivy, please refer to the <a href="../doc/concept.html">main concepts page</a>.
+<h2>Status</h2>
+A module status indicates how stable a module revision can be considered. It can 
+be used to consolidate the status of all the dependencies of a module, to prevent
+the use of an integration revision of a dependency in the release of your module.
+Three statuses are defined by default in ivy:
+<ul>
+<li>integration: revisions builded by a continuous build, a nightly build, and so on, fall in this category</li>
+<li>milestone: revisions delivered to the public but not actually finished fall in this category</li>
+<li>release: revision fully tested and labelled fall in this category</li>
+</ul>
+<span class="since">since 1.4</span> This list is <a href="../doc/configuration/statuses.html">configurable</a> in your configuration file.
+<h2>Repository</h2>
+What is called a repository in Ivy is a location where Ivy is able to find your modules artifacts and metadata (i.e. ivy files in most cases).
+Ivy can be used with complex repositories configured very finely. You can use <a href="../doc/concept.html">Dependency Resolvers</a> to do so.
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/terminology.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/tutorial.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/tutorial.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/tutorial.html (original)
+++ incubator/ivy/core/trunk/doc/doc/tutorial.html Wed May  9 03:58:10 2007
@@ -1,62 +1,62 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 1};</script>	
-	<script type="text/javascript" src="../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-The best way to learn is to practice! That's what the ivy tutorials will help you to do, to discover some of the great ivy <a href="../features.html">features</a>.
-
-Here is the very first tutorial, it doesn't even require to install Ivy, and should not take more than 30 seconds if you already have ant and a jdk properly installed:
-<ul>
-<li>make sure you have <a href="http://ant.apache.org/">ant</a> 1.6.2 or greater and a <a href="http://java.sun.com">jdk</a> properly installed</li>
-<li>copy <a href="../samples/build.xml">this build file</a> in an empty directory on your local filesystem (and make sure you name it build.xml)</li>
-<li>open a console in this directory and run "ant". That's it!</li>
-</ul>
-If you have any trouble, check the <a href="../faq.html">FAQ</a>, it may be related to your internet connection (proxy anyone?).
-
-OK, you've seen how easy it is to make your first step with ivy? Go ahead with the other tutorials, but before make sure you have properly <a href="install.html">installed</a> ivy and downloaded the tutorials sources (included in all ivy distributions, in the [[svn:src/example]] directory).
-
-The following tutorials are available:
-<ul>
-<li><a href="tutorial/start.html">Quick Start</a></li> 
-guide you through your very first steps with ivy.
-<li><a href="tutorial/ivyrep.html">Using IvyRep</a></li> 
-show you the out of the box power of ivy + ivyrep.
-<li><a href="tutorial/defaultconf.html">Configuring default resolver</a></li> 
-give you a better understanding of the default configuration and show you how to customize it to your needs.
-<li><a href="tutorial/multiple.html">Multiple Resolvers</a></li> 
-teach you how to configure Ivy to find its dependencies in multiple places.
-<li><a href="tutorial/dual.html">Dual Resolver</a></li> 
-help you configure ivy to find ivy files in one place and artifacts in another.
-<li><a href="tutorial/multi-project.html">Project Dependencies</a></li> 
-makes you touch the interest of using ivy in multi project environment.
-<li><a href="tutorial/conf.html">Using Ivy Configurations</a></li> 
-show how to use configurations in ivy file to define set of artifacts.
-<li><a href="tutorial/build-repository.html">Building a repository</a></li> 
-show how to build your own enterprise repository.
-</ul>
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+The best way to learn is to practice! That's what the ivy tutorials will help you to do, to discover some of the great ivy <a href="../features.html">features</a>.
+
+Here is the very first tutorial, it doesn't even require to install Ivy, and should not take more than 30 seconds if you already have ant and a jdk properly installed:
+<ul>
+<li>make sure you have <a href="http://ant.apache.org/">ant</a> 1.6.2 or greater and a <a href="http://java.sun.com">jdk</a> properly installed</li>
+<li>copy <a href="../samples/build.xml">this build file</a> in an empty directory on your local filesystem (and make sure you name it build.xml)</li>
+<li>open a console in this directory and run "ant". That's it!</li>
+</ul>
+If you have any trouble, check the <a href="../faq.html">FAQ</a>, it may be related to your internet connection (proxy anyone?).
+
+OK, you've seen how easy it is to make your first step with ivy? Go ahead with the other tutorials, but before make sure you have properly <a href="install.html">installed</a> ivy and downloaded the tutorials sources (included in all ivy distributions, in the [[svn:src/example]] directory).
+
+The following tutorials are available:
+<ul>
+<li><a href="tutorial/start.html">Quick Start</a></li> 
+guide you through your very first steps with ivy.
+<li><a href="tutorial/ivyrep.html">Using IvyRep</a></li> 
+show you the out of the box power of ivy + ivyrep.
+<li><a href="tutorial/defaultconf.html">Configuring default resolver</a></li> 
+give you a better understanding of the default configuration and show you how to customize it to your needs.
+<li><a href="tutorial/multiple.html">Multiple Resolvers</a></li> 
+teach you how to configure Ivy to find its dependencies in multiple places.
+<li><a href="tutorial/dual.html">Dual Resolver</a></li> 
+help you configure ivy to find ivy files in one place and artifacts in another.
+<li><a href="tutorial/multi-project.html">Project Dependencies</a></li> 
+makes you touch the interest of using ivy in multi project environment.
+<li><a href="tutorial/conf.html">Using Ivy Configurations</a></li> 
+show how to use configurations in ivy file to define set of artifacts.
+<li><a href="tutorial/build-repository.html">Building a repository</a></li> 
+show how to build your own enterprise repository.
+</ul>
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/tutorial.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/tutorial/build-repository.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/tutorial/build-repository.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/tutorial/build-repository.html (original)
+++ incubator/ivy/core/trunk/doc/doc/tutorial/build-repository.html Wed May  9 03:58:10 2007
@@ -1,61 +1,61 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-With the <a href="../../doc/use/install.html">install</a> ant task you are given the possibility to copy ivy descriptors and artifacts found from a resolver and publish them into another resolver.<br/> 
-
-This tutorial will show you how to build your own clean enterprise repository of ivy descriptors and modules artifacts.
-We will first use some basic ivy settings files to show how it works, and then we will use advanced features like <a href="../../doc/configuration/namespaces.html">namespaces</a> to build a real enterprise repository.
-
-<h1>The project used</h1>
-The project that we will use is quite simple.
-It is composed of an ant build file, and some ivy settings files.
-
-Here are the accessible target that we will use : 
-<div class="shell"><pre>
-Z:\ivy-repository>ant -p
-Buildfile: build.xml
-
-Main targets:
-
- advanced                                 --> retrieve files from public repositories (ivyrep, ibiblio, ...) using namespaces
- basic                                    --> retrieve files from well formatted ivy repositories
- basic-deps                               --> retrieve files from well formatted ivy repositories with dependencies
- clean-cache                              --> clean the cache
- clean-repo                               --> clean the destination repository
- commons-lang-1-0-ibiblio-no-namespace    --> retrieve commons-lang 1.0 from ibiblio maven using no namespaces
- commons-lang-1-0-ibiblio-with-namespace  --> retrieve commons-lang 1.0 from ibiblio maven using namespaces
- maven1                                   --> retrieve commons-lang 1.0 from maven1 repo using namespaces
- maven2                                   --> retrieve files from maven2 repo using namespaces
-Default target: basic</pre></div>
-<br/><br/>
-The project is accessible in the <a href="/latest/ivy">sources</a> of Ivy into : IVY_HOME/src/example/build-a-ivy-repository
-
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+With the <a href="../../doc/use/install.html">install</a> ant task you are given the possibility to copy ivy descriptors and artifacts found from a resolver and publish them into another resolver.<br/> 
+
+This tutorial will show you how to build your own clean enterprise repository of ivy descriptors and modules artifacts.
+We will first use some basic ivy settings files to show how it works, and then we will use advanced features like <a href="../../doc/configuration/namespaces.html">namespaces</a> to build a real enterprise repository.
+
+<h1>The project used</h1>
+The project that we will use is quite simple.
+It is composed of an ant build file, and some ivy settings files.
+
+Here are the accessible target that we will use : 
+<div class="shell"><pre>
+Z:\ivy-repository>ant -p
+Buildfile: build.xml
+
+Main targets:
+
+ advanced                                 --> retrieve files from public repositories (ivyrep, ibiblio, ...) using namespaces
+ basic                                    --> retrieve files from well formatted ivy repositories
+ basic-deps                               --> retrieve files from well formatted ivy repositories with dependencies
+ clean-cache                              --> clean the cache
+ clean-repo                               --> clean the destination repository
+ commons-lang-1-0-ibiblio-no-namespace    --> retrieve commons-lang 1.0 from ibiblio maven using no namespaces
+ commons-lang-1-0-ibiblio-with-namespace  --> retrieve commons-lang 1.0 from ibiblio maven using namespaces
+ maven1                                   --> retrieve commons-lang 1.0 from maven1 repo using namespaces
+ maven2                                   --> retrieve files from maven2 repo using namespaces
+Default target: basic</pre></div>
+<br/><br/>
+The project is accessible in the <a href="/latest/ivy">sources</a> of Ivy into : IVY_HOME/src/example/build-a-ivy-repository
+
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/tutorial/build-repository.html
------------------------------------------------------------------------------
    svn:eol-style = LF



Mime
View raw message