tamaya-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ple...@apache.org
Subject incubator-tamaya git commit: TAMAYA-95 Enabled property substitution on the front page.
Date Wed, 13 Apr 2016 08:33:48 GMT
Repository: incubator-tamaya
Updated Branches:
  refs/heads/master f721723c6 -> 4e92e8bcd


TAMAYA-95 Enabled property substitution on the front page.


Project: http://git-wip-us.apache.org/repos/asf/incubator-tamaya/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-tamaya/commit/4e92e8bc
Tree: http://git-wip-us.apache.org/repos/asf/incubator-tamaya/tree/4e92e8bc
Diff: http://git-wip-us.apache.org/repos/asf/incubator-tamaya/diff/4e92e8bc

Branch: refs/heads/master
Commit: 4e92e8bcd74aede5c06261a748880b9d117caabd
Parents: f721723
Author: Oliver B. Fischer <plexus@apache.org>
Authored: Tue Apr 12 22:33:10 2016 +0200
Committer: Oliver B. Fischer <plexus@apache.org>
Committed: Tue Apr 12 22:33:10 2016 +0200

----------------------------------------------------------------------
 pom.xml                       |  1 +
 src/site/markdown/index.md    | 48 ----------------------------------
 src/site/markdown/index.md.vm | 53 ++++++++++++++++++++++++++++++++++++++
 src/site/site.xml             |  4 +--
 4 files changed, 56 insertions(+), 50 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-tamaya/blob/4e92e8bc/pom.xml
----------------------------------------------------------------------
diff --git a/pom.xml b/pom.xml
index 95fda8d..cb8746d 100644
--- a/pom.xml
+++ b/pom.xml
@@ -690,6 +690,7 @@ under the License.
                         <exclude>**/*.json</exclude>
                         <exclude>**/*.adoc</exclude>
                         <exclude>**/*.md</exclude>
+                        <exclude>**/*.md.vm</exclude>
                         <!-- json can't get comments -->
                     </excludes>
                 </configuration>

http://git-wip-us.apache.org/repos/asf/incubator-tamaya/blob/4e92e8bc/src/site/markdown/index.md
----------------------------------------------------------------------
diff --git a/src/site/markdown/index.md b/src/site/markdown/index.md
deleted file mode 100644
index 39c691e..0000000
--- a/src/site/markdown/index.md
+++ /dev/null
@@ -1,48 +0,0 @@
-## About Apache Tamaya
-
-Tamaya provides a flexible and powerful Configuration Solution 
-for Java developers using Java SE as well as for more complex 
-usage scenarios like Cloud or Java EE. It provides a modern 
-type-safe property based Configuration API combined with a 
-powerful environment model and a flexible SPI. 
-
-## Features
-
-* Unified Configuration API
-* Pluggable Configuration Backends
-* Enforceable Configuration Policies
-* Configuration Validation and Documentation
-* Seemless Enterprise Integration
-
-## Documentation
-
-* [Use Cases and Requirements](usecasesAnd Reqs.html)
-* [High Level Design](HighLevelDesign.html)
-* [API](API.html)
-* [Core](Core.html)
-* [Extensions](extensions.html)
-
----
-
-## Quickstart
-
-Using Apache Tamaya is simple:
-
-1. Add `org.apache.tamaya:tamaya-core:{tamaya-version}` to your dependencies.
-2. Add your config to `META-INF/javaconfiguration.properties`
-3. Access your configuration by `ConfigurationProvider.getConfiguration()` and use it.
-4. Look at the [extension modules](extensions.html) to customize your setup!
-5. Enjoy!
-
-
-## Rationale
-
-Configuration is one of the most prominent cross-cutting concerns similar to logging. Most
of us already have been
-writing similar code again and again in each of our projects. Sometimes in a similar way
but mostly always slightly
-different, but certainly with high coupling to your configuration backends. Given your code
is reused or integrated
-some how, or deployed by some customers, struggling starts: not supported backends, different
policies, missing
-combination and validation mechanisms and so on. Tamaya solves all this by defining a common
API and backend SPI.
-Your code is decoupled from the configuratoin backend. There is no difference if your code
is deployed on your dev box
-or in a clustered Docker environment in production, it stays the same!
-
-

http://git-wip-us.apache.org/repos/asf/incubator-tamaya/blob/4e92e8bc/src/site/markdown/index.md.vm
----------------------------------------------------------------------
diff --git a/src/site/markdown/index.md.vm b/src/site/markdown/index.md.vm
new file mode 100644
index 0000000..c740154
--- /dev/null
+++ b/src/site/markdown/index.md.vm
@@ -0,0 +1,53 @@
+About Apache Tamaya
+-------------------
+
+Tamaya provides a flexible and powerful Configuration Solution 
+for Java developers using Java SE as well as for more complex 
+usage scenarios like Cloud or Java EE. It provides a modern 
+type-safe property based Configuration API combined with a 
+powerful environment model and a flexible SPI. 
+
+Features
+--------
+
+* Unified Configuration API
+* Pluggable Configuration Backends
+* Enforceable Configuration Policies
+* Configuration Validation and Documentation
+* Seemless Enterprise Integration
+
+Documentation
+-------------
+
+* [Use Cases and Requirements](usecasesAnd Reqs.html)
+* [High Level Design](HighLevelDesign.html)
+* [API](API.html)
+* [Core](Core.html)
+* [Extensions](extensions.html)
+
+---
+
+Quickstart
+----------
+
+Using Apache Tamaya is simple:
+
+1. Add `org.apache.tamaya:tamaya-core:${project.version}` to your dependencies.
+2. Add your config to `META-INF/javaconfiguration.properties`
+3. Access your configuration by `ConfigurationProvider.getConfiguration()` and use it.
+4. Look at the [extension modules](extensions.html) to customize your setup!
+5. Enjoy!
+
+
+Rationale
+---------
+
+Configuration is one of the most prominent cross-cutting concerns similar to logging. Most
of us already have been
+writing similar code again and again in each of our projects. Sometimes in a similar way
but mostly always slightly
+different, but certainly with high coupling to your configuration backends. Given your code
is reused or integrated
+some how, or deployed by some customers, struggling starts: not supported backends, different
policies, missing
+combination and validation mechanisms and so on. Tamaya solves all this by defining a common
API and backend SPI.
+Your code is decoupled from the configuratoin backend. There is no difference if your code
is deployed on your dev box
+or in a clustered Docker environment in production, it stays the same!
+
+

http://git-wip-us.apache.org/repos/asf/incubator-tamaya/blob/4e92e8bc/src/site/site.xml
----------------------------------------------------------------------
diff --git a/src/site/site.xml b/src/site/site.xml
index 0710227..b0fb6c2 100644
--- a/src/site/site.xml
+++ b/src/site/site.xml
@@ -45,7 +45,7 @@ under the License.
             <item name="Core" href="Core.html"/>
             <item name="Extension Guide" href="extensions.html"/>
             <item name="Design Guide" href="HighLevelDesign.html"/>
-            <item name="${project.version} JavaDoc" target="" href="apidocs/index.html"/>
+            <item name="JavaDoc of ${project.version}" target="" href="apidocs/index.html"/>
         </menu>
 
         <menu name="Development">
@@ -99,4 +99,4 @@ under the License.
             <theme>bootswatch-cosmo</theme>
         </reflowSkin>
     </custom>
-</project>
\ No newline at end of file
+</project>


Mime
View raw message