natas_hw
/
ant-ivy
mirror of https://github.com/apache/ant-ivy
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

IMPROVEMENT: Support atomic publish with sub directory structure (IVY-856) 

git-svn-id: https://svn.apache.org/repos/asf/ant/ivy/core/trunk@674785 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Xavier Hanin 2008-07-08 12:04:47 +00:00
parent 46fe473ebf
commit b30acb3f75
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/resolver/filesystem.html
View File

@ -45,7 +45,7 @@ In this case the resolver starts by publishing the module according to the patte
<b>Limitations</b>
Atomic publish is currently limited in several ways:
<ul>
<li>you need to use a pattern for both the artifact and the ivy files which uses the revision as last directory. For instance [module]/[revision]/[artifact].[ext] works, [module]/[artifact]-[revision].[ext] doesn't</li>
<li>you need to use a pattern for both the artifact and the ivy files which uses the revision as a directory. For instance [module]/[revision]/[artifact].[ext] works, [module]/[artifact]-[revision].[ext] doesn't</li>
<li>both the artifact and ivy pattern should have the same prefix until the [revision] token.</li>
<li>overwrite during publish is not supported</li>
<li>you should not use revision names ending with '.part'</li>
@ -54,7 +54,7 @@ Atomic publish is currently limited in several ways:
The <b>transactional</b> attribute can be used to configure the atomicity behavior:
<ul>
<li>auto</li> use transaction if possible (according to limitation), otherwise don't
<li>true</li> always use transaction, fail the build if a limitation is is not fulfilled
<li>true</li> always use transaction, fail the build if a limitation is not fulfilled
<li>false</li> don't use transaction at all
</ul>
@ -68,7 +68,7 @@ This resolver shares the <a href="../configuration/resolvers.html#common">common
<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>
<tr><td>local</td><td>True if this resolver should be considered local, false otherwise <span class="since">since 1.4</span>. See useOrigin attribute on the [[ant:resolve]] task for details.</td>
<tr><td>local</td><td>True if this resolver should be considered local, false otherwise <span class="since">since 1.4</span>. See useOrigin attribute on the [[configuration/caches]] element for details.</td>
<td>No, defaults to true</td></tr>
<tr><td>transactional</td><td>true to force the use of transaction, false to prevent the use of transaction, auto to get transaction when possible <span class="since">since 2.0</span>. See above for details.</td>
<td>No, defaults to auto</td></tr>