Repository: ant-ivy Updated Branches: refs/heads/master 9e1b0896c -> 614bf1ad5
http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/614bf1ad/asciidoc/use/var.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/use/var.adoc b/asciidoc/use/var.adoc index 7fc4e96..79e6c25 100644 --- a/asciidoc/use/var.adoc +++ b/asciidoc/use/var.adoc @@ -17,11 +17,11 @@ under the License. //// -Sets a variable (by name and value), or set of variables (from file or url) in Ivy. +Sets a variable (by name and value), or set of variables (from file or URL) in Ivy. Variables are case sensitive. -Contrary to ant properties, ivy variables are mutable. But a problem with this is that you do not control when +Contrary to Ant properties, Ivy variables are mutable. But a problem with this is that you do not control when variables are substituted, and usually it is done as soon as possible. So changing the value of a variable will have no effect if it has already been substituted. Consequently, *using this task is NOT recommended*. @@ -34,9 +34,9 @@ See link:../reference.html[reference] page for details about Ivy variables. |Attribute|Description|Required |name|the name of the variable to set|No |value|the value of the variable to set|Yes when using the name attribute -|file|the filename of the property file to load as ivy variables +|file|the filename of the property file to load as Ivy variables .2+.^|One of these, when *not* using the name attribute -|url|the url from which to read ivy variables +|url|the URL from which to read Ivy variables |prefix|Prefix to apply to variables. A dot (`.`) is appended to the prefix if not specified.|No -|settingsRef|A reference to the ivy settings that must be used by this task *__(since 2.0)__*|No, defaults to `ivy.instance`. +|settingsRef|A reference to Ivy settings that must be used by this task *__(since 2.0)__*|No, defaults to `ivy.instance`. |======= http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/614bf1ad/asciidoc/yed.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/yed.adoc b/asciidoc/yed.adoc index 8c7c4e1..1e9bd74 100644 --- a/asciidoc/yed.adoc +++ b/asciidoc/yed.adoc @@ -24,11 +24,11 @@ The graphs generated by Ivy are not laid out (in fact it's why we use yEd), so y == Preparation -First you have to generate a graphml file. Simply call the report task (see ivy use documentation) for that. +First you have to generate a GraphML file. Simply call the report task (see ivy use documentation) for that. -== Step 1: open the graphml file +== Step 1: open the GraphML file -Launch yEd editor, and open the graphml file generated by the report task. You should obtain something like this: +Launch yEd editor, and open the GraphML file generated by the report task. You should obtain something like this: image::images/yed-step1.jpg[] @@ -53,4 +53,4 @@ That's all, you should have obtained something like this: image::images/yed-step7.jpg[] Note that this is only one possibility, test the available layouts yourself, you could find one better in your case. -Once you have laid out the graph, you can either save it with in the same file (but be warned that it will be overwritten at next ivy report call), or another file, export it to jpg, gif, svg, etc. (see link:http://www.yworks.com/en/products_yed_about.htm[yEd] site for details). +Once you have laid out the graph, you can either save it with in the same file (but be warned that it will be overwritten at next Ivy report call), or another file, export it to JPEG, GIF, SVG, etc. (see link:http://www.yworks.com/en/products_yed_about.htm[yEd] site for details).
