You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by sm...@apache.org on 2016/04/02 16:46:05 UTC
directory-fortress-core git commit: FC-164 - change README-CONFIG to
point to renamed ant build-config.xml
Repository: directory-fortress-core
Updated Branches:
refs/heads/master 5f55215e4 -> 5bb8ae34a
FC-164 - change README-CONFIG to point to renamed ant build-config.xml
Project: http://git-wip-us.apache.org/repos/asf/directory-fortress-core/repo
Commit: http://git-wip-us.apache.org/repos/asf/directory-fortress-core/commit/5bb8ae34
Tree: http://git-wip-us.apache.org/repos/asf/directory-fortress-core/tree/5bb8ae34
Diff: http://git-wip-us.apache.org/repos/asf/directory-fortress-core/diff/5bb8ae34
Branch: refs/heads/master
Commit: 5bb8ae34a6c17a1c9fd629760b0720143455dcc5
Parents: 5f55215
Author: Shawn McKinney <sm...@apache.org>
Authored: Sat Apr 2 09:46:00 2016 -0500
Committer: Shawn McKinney <sm...@apache.org>
Committed: Sat Apr 2 09:46:00 2016 -0500
----------------------------------------------------------------------
README-CONFIG.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/directory-fortress-core/blob/5bb8ae34/README-CONFIG.md
----------------------------------------------------------------------
diff --git a/README-CONFIG.md b/README-CONFIG.md
index d11ec55..aeb541b 100644
--- a/README-CONFIG.md
+++ b/README-CONFIG.md
@@ -38,7 +38,7 @@ Fortress uses the following source property files to bootstrap configuration:
* [slapd.properties](./slapd.properties.example)
* [build.properties](./build.properties.example)
2. Apache Ant script:
- * [build.xml](./build.xml)
+ * [build-config.xml](./build-config.xml)
Which are used to produce new artifacts used by Fortress runtime:
@@ -143,7 +143,7 @@ B just updates the config node with the new values, preserving the other data.
* Another option is to use a script like **ConfigNodeUpdate.xml** to perform the CRUD ops.
* You can also *simply* place the properties inside the fortress.properties file (only). The idea is to minimize the number of locations
where the same data must be stored. Imagine a network with hundreds, even thousands of fortress agents running. We don't need to replicate the same data everywhere which is where remote config nodes help.
- * For more info on which parameters are used where, look at the **init-fortress-config** target located inside the [build.xml](build.xml) file.
+ * For more info on which parameters are used where, look at the **init-fortress-config** target located inside the [build-config.xml](build-config.xml) file.
___________________________________________________________________________________
#### END OF README-CONFIG
\ No newline at end of file