svn commit: r35417 - /dev/incubator/tamaya/0.4-incubating/apiandcore/
Author: anatole Date: Wed Aug 28 00:59:46 2019 New Revision: 35417 Log: TAMAYA-408 Preparing release. Modified: dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.tar.gz dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.tar.gz.asc dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.zip dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.zip.asc Modified: dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.tar.gz == Binary files - no diff available. Modified: dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.tar.gz.asc == --- dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.tar.gz.asc (original) +++ dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.tar.gz.asc Wed Aug 28 00:59:46 2019 @@ -1,11 +1,16 @@ -BEGIN PGP SIGNATURE- -iQEzBAABCgAdFiEEdUobk8nV1VNIKm+uWzij6v6dAYsFAl1kWTwACgkQWzij6v6d -AYsz8wf/a7ZAsSvnTN5DLMN5OGvh5I9QY6+x5WDnQMJKU/mgnuW45ETPG+lIWrjB -apFPGx246IQDtF9iCzKfkak27qkNefbATNdcYGBlRS0RpmV7y58o0HTxVlODqzNX -Mjki1oE4+Sddk/6EldJ6HsZD43gZna3t5dTc7i6cmkH+Q1q7Nsw21L1Z38aGoLxD -FhvXHc8t+AWbZYLBhUImaYOCPy4gt0G2P0tdjUkWP+ParMOL5RBPIf5J+daDGryu -MwVdMpegJU6CnqKknj/XUdFNFwZpy2b4FLRt301Mofdo7z/xMUbcZsalISYfmUds -bXkGICFylMUIIfG1sRPqZCCQ+oJ01Q== -=zbkh +iQIzBAABCgAdFiEEpWjBXASsQX7qY3C/J5ELohM20+YFAl1lxjAACgkQJ5ELohM2 +0+Yy6xAApBFWbclqp50nixoGnZ87t+OvAzSHlN/+82cmaIG64+hy0G6D2P0HXdMj +TjMwrspydNKDrDQxWixBi0TpRFU8Iob4eosFkLuaSKim9p6KnKukWPzUo4IiGUGW ++qoj9ESH6xUuLbG8JamDCdaCqzQNr9K9Ny9kMXQqeIwlSUgUkk+2xHn9R7D7Q4jr ++4X5+o/d3yFfypte52G8Ge673chBaiKDX6WGpjgZrNbE6z2o3rHxx4iRTyX+ojCf +AGS+SXeTK9ezqKNXgEHkFCzpF0uN37QFqzl4psf2+yOSYiESvC8e6CdbMjfemtA1 +lF7+rOTR0UiDmsuwLRSvBmXJPQnH8RB/zFaNw+JsLCZZLf7BlmBi1/TtOi9IOMti +cGyf8yWBxpEg4inbdq/5amscUUBcRbiyKXEUOUbKGvUBz53WkL0ZgFtGEplCMT95 +yiIbwlKCshFdvaVjvHHKIYG5LTXP5H7ZhvaLWT8zO50eCb4zcrmb+FHAFNMy1o43 +iExzG/m8vOhTHRjh4ZKxUImQfCgQvWJO+m2OrtBdDt1calb/TxgUqEsDJIU5KFTW +k0V4AvXs5DqRPf2U5MjzptFHPI9D3LBxAKShpJMNDQhJDitZaioejXWEv1KERPpr +m41gaT4UAV5oji9dCZ7rm1/AQGBMwWwdCHif1mCFA9w8GdQ5OMk= +=nDgH -END PGP SIGNATURE- Modified: dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.zip == Binary files - no diff available. Modified: dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.zip.asc == --- dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.zip.asc (original) +++ dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.zip.asc Wed Aug 28 00:59:46 2019 @@ -1,11 +1,16 @@ -BEGIN PGP SIGNATURE- -iQEyBAABCgAdFiEEdUobk8nV1VNIKm+uWzij6v6dAYsFAl1kWTsACgkQWzij6v6d -AYt4egf48E17ffXFxzixPmF+TLU7R8Wf+7UkbgKqg8/j6FYgOyyu1H2mikOJMHZn -/VkzFJpxu5t1HdD4zxaKnbHqcgMPB2IQ1lEGTa7pjwgnKii+JvScM990xGdMyJzD -cy9L5D5KIftxRhcNHb4/cHpLpzeZVYCTHMVWDOpM+W6moScUTEyOaYHsVni8TgHZ -Cg+jExtvPVGz0pCb8yQtdhu8bvq39kYOF5M/CxeTrVot4FHI/mXecDbRVObakQ+f -aCpGM+vBDdO8pbv6U5PTt6yWNb84BYVvpV7BZTM3ubsLmTXmVREnCl+rsrPfwHxt -rtOeUACMuEqTqDtZb3/fRXKnJVA/ -=8lFn +iQIzBAABCgAdFiEEpWjBXASsQX7qY3C/J5ELohM20+YFAl1lxi8ACgkQJ5ELohM2 +0+YMGw//dSk329frXYheDjTZVZDa7UOoiOfmsy7i7ChLjevdgxGbgugcgrn8IGDN +ZXe7Qw/jR0UoyJKYMLFIWTVs/zaKP8CmysYPpSxMYZ5h3s/3XVEiDUmmyM2mGJBH +li9kvaLmbD94aU9RrvtNMBoJcJFBkRDDPdwwhtPDJvqMOIxweR+pHmaMe25sk8Y9 +cEryr6F/TX6WFz/2vyVig/vg26pk6WesWfmG2R+lQNZc2GVR1QvRD+W+Fzon9bMj +nQRpQ2N3JqSigx1u39eWMYupSraryAQYCCsEGklk6pBcOZSCHEEI7dsLvpgukfrW +B6q1EA3rl5qFq0PZJR2w3B/eaNc2LQPGbMMN2OOlOkkHbfSgF34cmgeAaJIkHuVs +e/D2otItAKJfgTpV5RBcUE+ciFRXWWF1RNgLGdEjbPYWJ/hhWf8W6Pn1TlqJiRf2 +Hq+xWyjIqn61PSII3zHmH/4hKh9wvD7J8n9VBG5L4SBRgA2eR6DTIS6+aYn1Syee +RvaDqPHGTrXH+gTZhpkONvG3kc+1R2IHf+w57yrTs/0pMGSEqeoXMKsS2CMaZtNP +0p8OIfhVTKX5vTEp9fE4+/6vWkideABgX+L5QijUfYkFph0h+hAydmJeGInzssIp +/uvV5iVuGe1gYG3FKfTxOrWWuGwszgMTrqck1BuJXEHT32TUoXY= +=YJYT -END PGP SIGNATURE-
[incubator-tamaya-extensions] branch vote-0.4-incubating-RC3 created (now 73f6f56)
This is an automated email from the ASF dual-hosted git repository. anatole pushed a change to branch vote-0.4-incubating-RC3 in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-extensions.git. at 73f6f56 TAMAYA-408 Preparing release, removing snapshoz refs. No new revisions were added by this update.
[incubator-tamaya-sandbox] branch vote-0.4-incubating-RC3 created (now 309c334)
This is an automated email from the ASF dual-hosted git repository. anatole pushed a change to branch vote-0.4-incubating-RC3 in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-sandbox.git. at 309c334 Disabled withdrawn config jsr. No new revisions were added by this update.
[incubator-tamaya-site] branch vote-0.4-incubating-RC3 created (now c1eabf9)
This is an automated email from the ASF dual-hosted git repository. anatole pushed a change to branch vote-0.4-incubating-RC3 in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git. at c1eabf9 Updated release guide. No new revisions were added by this update.
[incubator-tamaya] branch vote-0.4-incubating-RC3 created (now d2d6078)
This is an automated email from the ASF dual-hosted git repository. anatole pushed a change to branch vote-0.4-incubating-RC3 in repository https://gitbox.apache.org/repos/asf/incubator-tamaya.git. at d2d6078 TAMAYA-408 Preparing release. No new revisions were added by this update.
[incubator-tamaya] tag vote-0.4-incubating-RC3 created (now d2d6078)
This is an automated email from the ASF dual-hosted git repository. anatole pushed a change to tag vote-0.4-incubating-RC3 in repository https://gitbox.apache.org/repos/asf/incubator-tamaya.git. at d2d6078 (commit) No new revisions were added by this update.
[incubator-tamaya-site] branch vote-0.4-incubating-01 updated: TAMAYA-279: Add current RC to release history
This is an automated email from the ASF dual-hosted git repository. pottlinger pushed a commit to branch vote-0.4-incubating-01 in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git The following commit(s) were added to refs/heads/vote-0.4-incubating-01 by this push: new df00424 TAMAYA-279: Add current RC to release history df00424 is described below commit df00424779ba958cab5a765669b8a2c48479aef2 Author: Hugo Hirsch AuthorDate: Tue Aug 27 23:36:07 2019 +0200 TAMAYA-279: Add current RC to release history --- content/history.adoc | 5 + 1 file changed, 5 insertions(+) diff --git a/content/history.adoc b/content/history.adoc index 68a04b8..d5142aa 100644 --- a/content/history.adoc +++ b/content/history.adoc @@ -16,6 +16,11 @@ Overview of all released versions of Apache Tamaya. | Release Notes | Download +| 0.4-incubating +| 2019-08-xx +| n/a +| https://archive.apache.org/dist/incubator/tamaya/0.4-incubating/[Download of 0.4 incubating^] + | 0.3-incubating | 2016-09-12 | n/a
[incubator-tamaya-site] branch vote-0.4-incubating-01 updated: TAMAYA-411: Update docs about Javadoc generation and change URL to https
This is an automated email from the ASF dual-hosted git repository. pottlinger pushed a commit to branch vote-0.4-incubating-01 in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git The following commit(s) were added to refs/heads/vote-0.4-incubating-01 by this push: new 94979a2 TAMAYA-411: Update docs about Javadoc generation and change URL to https 94979a2 is described below commit 94979a24b17dfb6bd51ce22fcd3d514555b13abb Author: Hugo Hirsch AuthorDate: Tue Aug 27 23:33:11 2019 +0200 TAMAYA-411: Update docs about Javadoc generation and change URL to https --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 26ddcf9..24c765c 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,7 @@ Contains the jbake original files and all binaries (images, fonts, static JS) an Templates -All [Thymeleaf-based](http://www.thymeleaf.org/) page templates can be found in the `templates` directory. These templates are footer, header and menu of the website. +All [Thymeleaf-based](https://www.thymeleaf.org/) page templates can be found in the `templates` directory. These templates are footer, header and menu of the website. Template variables @@ -65,7 +65,7 @@ You need write access to this repository and have to generate the javadoc manual ``` $ cd tamaya $ git checkout master (to generate the current development version) OR -$ git checkout 0.3-incubating (to generate the a stable release version) +$ git checkout 0.4-incubating (to generate the a stable release version) $ mvn site (since javadoc:javadoc does not generate a full report) ```
[incubator-tamaya-site] branch vote-0.4-incubating-01 updated: TAMAYA-411: Prepare javadoc versions after new release
This is an automated email from the ASF dual-hosted git repository. pottlinger pushed a commit to branch vote-0.4-incubating-01 in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git The following commit(s) were added to refs/heads/vote-0.4-incubating-01 by this push: new d8f950b TAMAYA-411: Prepare javadoc versions after new release d8f950b is described below commit d8f950b6c155c7a48d5ad0163d2b85988b82d6ea Author: Hugo Hirsch AuthorDate: Tue Aug 27 23:31:48 2019 +0200 TAMAYA-411: Prepare javadoc versions after new release --- jbake.properties | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/jbake.properties b/jbake.properties index 5a868b7..f831bb5 100644 --- a/jbake.properties +++ b/jbake.properties @@ -16,7 +16,7 @@ template.encoding=UTF-8 # Make properties available in templates asciidoctor.attributes.export=true twitterhandle=tamayaconf -tamaya_version_released=0.3-incubating -tamaya_version_development=0.4-incubating-SNAPSHOT +tamaya_version_released=0.4-incubating +tamaya_version_development=0.5-incubating-SNAPSHOT tamaya_version=0.4-incubating-SNAPSHOT tamaya_mvn_group_id=org.apache.tamaya
[incubator-tamaya-site] branch vote-0.4-incubating-01 updated: Fix missing version number replacement in new docs
This is an automated email from the ASF dual-hosted git repository.
pottlinger pushed a commit to branch vote-0.4-incubating-01
in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git
The following commit(s) were added to refs/heads/vote-0.4-incubating-01 by this
push:
new 4cff93c Fix missing version number replacement in new docs
4cff93c is described below
commit 4cff93ce8ba3eb7ff1736922c518ada61cb00a36
Author: Hugo Hirsch
AuthorDate: Tue Aug 27 23:25:46 2019 +0200
Fix missing version number replacement in new docs
---
content/documentation/extensions/mod_hjson.adoc | 2 +-
content/documentation/extensions/mod_hocon.adoc | 2 +-
content/documentation/extensions/mod_osgi.adoc | 8
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/documentation/extensions/mod_hjson.adoc
b/content/documentation/extensions/mod_hjson.adoc
index 5af7de4..965211d 100644
--- a/content/documentation/extensions/mod_hjson.adoc
+++ b/content/documentation/extensions/mod_hjson.adoc
@@ -51,7 +51,7 @@ The module is based on Java 8.
To use the HJSON extension module you only must add the corresponding
dependency to your project:
-[source, xml]
+[source, xml, subs=attributes+]
---
org.apache.tamaya.ext
diff --git a/content/documentation/extensions/mod_hocon.adoc
b/content/documentation/extensions/mod_hocon.adoc
index 3808b3d..332d0db 100644
--- a/content/documentation/extensions/mod_hocon.adoc
+++ b/content/documentation/extensions/mod_hocon.adoc
@@ -51,7 +51,7 @@ The module is based on Java 8.
To use the HOCON extension module you only must add the corresponding
dependency to your module:
-[source, xml]
+[source, xml, subs=attributes+]
---
org.apache.tamaya.ext
diff --git a/content/documentation/extensions/mod_osgi.adoc
b/content/documentation/extensions/mod_osgi.adoc
index 6d75a1a..b9e928e 100644
--- a/content/documentation/extensions/mod_osgi.adoc
+++ b/content/documentation/extensions/mod_osgi.adoc
@@ -432,22 +432,22 @@ public interface TamayaConfigService{
Finally Tamaya also provides support for using Tamaya's injection API with
your OSGi project. To enable injection
you must install a few additional bundles:
-[source, xml]
+[source, xml, subs=attributes+]
---
org.apache.tamaya.ext
tamaya-osgi-injection
- ${tamaya.version}
+ {tamaya_version}
org.apache.tamaya.ext
tamaya-injection
- ${tamaya.version}
+ {tamaya_version}
org.apache.tamaya.ext
injection-api
- ${tamaya.version}
+ {tamaya_version}
---
[incubator-tamaya-site] 04/08: Fix Tamaya as Standards, harmonize OSGi
This is an automated email from the ASF dual-hosted git repository. pottlinger pushed a commit to branch vote-0.4-incubating-01 in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git commit 8e59f81aba994c72781e91f255fd79d91b3da078 Author: Hugo Hirsch AuthorDate: Tue Aug 27 23:09:02 2019 +0200 Fix Tamaya as Standards, harmonize OSGi --- .../documentation/extensions/mod_usagetracker.adoc | 2 +- content/tamayaasastandard.adoc | 21 ++--- 2 files changed, 11 insertions(+), 12 deletions(-) diff --git a/content/documentation/extensions/mod_usagetracker.adoc b/content/documentation/extensions/mod_usagetracker.adoc index 395c048..00b6a65 100644 --- a/content/documentation/extensions/mod_usagetracker.adoc +++ b/content/documentation/extensions/mod_usagetracker.adoc @@ -148,7 +148,7 @@ DATE: Sat Apr 30 21:51:09 CEST 2016 A special feature of this module is that it observes +ConfigEvent+ published through Tamaya'as event channel (+tamaya-events+ module). If no metaconfiguration model is found the model manager by default automatically creates models for all injected instances on the fly. In the case of CDI integration this happens typically during deployment -time, since CDI initializes during deployment time. Other runtime platforms, such as OSGI, may have rather different +time, since CDI initializes during deployment time. Other runtime platforms, such as OSGi, may have rather different behaviour. Nevertheless this means that after your system has been started you should have access to a complete set of +ConfigModel+ instances that automatically document all the classes in your system that consume configuration (through injection). diff --git a/content/tamayaasastandard.adoc b/content/tamayaasastandard.adoc index 8d6a3a8..e026707 100644 --- a/content/tamayaasastandard.adoc +++ b/content/tamayaasastandard.adoc @@ -11,10 +11,10 @@ provide a long term stable configuration solution. Tamaya implements a recent state of the Configuration JSR. The exact commit version of the JSR API implemented (the JSR has not yet released any version -as of now) can be evaluated looing at the _tamaya-jsr382_ `pom.xml` in the +as of now) can be evaluated by looking at the _tamaya-jsr382_ `pom.xml` in the sandbox repository. -To use Tamaya aS a JSR-382 Configuration provider you must add the following +To use Tamaya as a JSR-382 Configuration provider you must add the following dependency: [source,xml] @@ -27,8 +27,7 @@ dependency: - Since this component is not yet officially released you must use the current snapshot -version +0.4-incubating-SNAPSHOT+. You also must add the Apache Snapshot -Repository to your build: +version +0.4-incubating-SNAPSHOT+. In order for that to work, you need to add the Apache Snapshot Repository to your build: [source,xml] - @@ -46,7 +45,7 @@ Repository to your build: - -== Microprofile +== Microprofile Configuration API Tamaya implements the Microprofile Configuration API Version 1.1. To use Tamaya as a Micropropfile Configuration provider you must add the following dependency: @@ -61,14 +60,14 @@ as a Micropropfile Configuration provider you must add the following dependency: - -== OSGI ConfigAdmin +== OSGi ConfigAdmin -Tamaya's OSGI Support leverages the OSGI +org.osgi.service.cm.ConfigurationAdmin+ -configuration manager as defined in OSGI Compendiumn Version +4.3.1+. Hereby -Tamaya can add or modify Configuration in OSGI, which may trigger change events. +Tamaya's OSGi Support leverages the OSGi +org.osgi.service.cm.ConfigurationAdmin+ +configuration manager as defined in OSGi Compendium Version +4.3.1+. Hereby +Tamaya can add or modify Configuration in OSGi, which may trigger change events. The exact behaviour can be controlled in many ways. By default Tamaya, does not change -anything, when deployed in OSGI, without being configured todo so. For details -check link:documentation/extensions/mod_osgi.html[Tamaya's OSGI Documentation]. +anything, when deployed in OSGi, without being configured todo so. For details +check link:documentation/extensions/mod_osgi.html[Tamaya's OSGi Documentation].
[incubator-tamaya-site] 02/08: Fix typos in JSON doc
This is an automated email from the ASF dual-hosted git repository. pottlinger pushed a commit to branch vote-0.4-incubating-01 in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git commit fc1797606e1a02599efacb7450b263f5f6bc6431 Author: Hugo Hirsch AuthorDate: Tue Aug 27 23:00:59 2019 +0200 Fix typos in JSON doc --- content/documentation/extensions/mod_json.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/documentation/extensions/mod_json.adoc b/content/documentation/extensions/mod_json.adoc index adb2ecb..3d7c7d5 100644 --- a/content/documentation/extensions/mod_json.adoc +++ b/content/documentation/extensions/mod_json.adoc @@ -10,9 +10,9 @@ toc::[] == Tamaya JSON (Extension Module) Tamaya _JSON_ is an extension module. Refer also to the link:../extensions.html[extensions documentation] for further details. -=== What functionality this module provides ? +=== What functionality does this module provide? -Tamaya _JSON_ provides support for reading configuration in JSON (Java Serializued Object Notation): +Tamaya _JSON_ provides support for reading configuration in JSON (Java Serialized Object Notation): [source, json] --- @@ -26,7 +26,7 @@ Tamaya _JSON_ provides support for reading configuration in JSON (Java Serializu Hereby the hierarchical structure of the JSON document will be mapped to a corresponding `PropertyValue` tree structure. This strucuture can be mapped -to flat key-value pairs of type `String`, e.g. the bove will be mapped to +to flat key-value pairs of type `String`, e.g. the above will be mapped to [source, properties] ---
[incubator-tamaya-site] 06/08: Harmonize OSGi
This is an automated email from the ASF dual-hosted git repository.
pottlinger pushed a commit to branch vote-0.4-incubating-01
in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git
commit 7f5b8b0016175391915b5fc25e8043dc130ad36d
Author: Hugo Hirsch
AuthorDate: Tue Aug 27 23:11:11 2019 +0200
Harmonize OSGi
---
content/documentation/extensions/mod_cdi.adoc | 2 +-
content/documentation/extensions/mod_features.adoc | 4 ++--
content/documentation/extensions/mod_injection.adoc | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/documentation/extensions/mod_cdi.adoc
b/content/documentation/extensions/mod_cdi.adoc
index 8d2c0c6..c609668 100644
--- a/content/documentation/extensions/mod_cdi.adoc
+++ b/content/documentation/extensions/mod_cdi.adoc
@@ -27,7 +27,7 @@ Hereby there are two implementations provided:
* +tamaya-injection-cdi+ implements injection by using CDI's injection
mechanism to inject configuration values into the
beans managed by the CDI systems.
* +tamaya-injection-standalone+ implements injection by integrating the
+tamaya-injection+ SE based injection module (also used
- for Spring and OSGI injection) with CDI. Injection hereby is performed by
the Tamaya SE module, whereas
+ for Spring and OSGi injection) with CDI. Injection hereby is performed by
the Tamaya SE module, whereas
beans and injection control overall are still managed by CDI.
* One difference, of course, is that +tamaya-injection-standalone+ also
provides an SE compatible API (+ConfigurationInjection,
ConfigurationInjector+), which is not available, when using the purely CDI
based variant.
diff --git a/content/documentation/extensions/mod_features.adoc
b/content/documentation/extensions/mod_features.adoc
index 4379fe5..e51c603 100644
--- a/content/documentation/extensions/mod_features.adoc
+++ b/content/documentation/extensions/mod_features.adoc
@@ -62,7 +62,7 @@ public final class Features {
public static boolean extSpringCoreAvailable();
public static boolean extJndiAvailable();
-public static boolean extOSGIAvailable();
+public static boolean extOSGiAvailable();
public static boolean checkClassIsLoadable(String classname);
}
@@ -83,5 +83,5 @@ public final class Features {
* +jndiAvailable();+ checks for the link:mod_jndi.html[_tamaya_jndi_] module.
* +extJndiAvailable();+ checks if creation of a new `InitialContext` is
successful.
* +extSpringCoreAvailable();+ checks if Spring Core is on the classpath.
-* +extOSGIAvailable();+ checks the OSGI framework is on the classpath.
+* +extOSGiAvailable();+ checks the OSGi framework is on the classpath.
* Finally +checkClassIsLoaded(String)+ tries to load a class. If it fails,
`false` is returned.
diff --git a/content/documentation/extensions/mod_injection.adoc
b/content/documentation/extensions/mod_injection.adoc
index 1581fc4..96958ef 100644
--- a/content/documentation/extensions/mod_injection.adoc
+++ b/content/documentation/extensions/mod_injection.adoc
@@ -141,7 +141,7 @@ ConfigurationInjector.getInstance().configure(tenant);
NOTE: Configuration injection works similarly, when used with other
integration modules, e.g. when Tamaya is used
-with CDI, Spring or within an OSGI container. For further details refer also
to the corresponding integration module's
+with CDI, Spring or within an OSGi container. For further details refer also
to the corresponding integration module's
documentation.
[incubator-tamaya-site] 03/08: Fix typos in docs
This is an automated email from the ASF dual-hosted git repository. pottlinger pushed a commit to branch vote-0.4-incubating-01 in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git commit 1e73bd25ebdacbe46b201cc7852cb1571a9be34d Author: Hugo Hirsch AuthorDate: Tue Aug 27 23:01:44 2019 +0200 Fix typos in docs --- content/documentation/extensions/mod_hjson.adoc | 2 +- content/documentation/extensions/mod_json.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/documentation/extensions/mod_hjson.adoc b/content/documentation/extensions/mod_hjson.adoc index 96a37cf..5af7de4 100644 --- a/content/documentation/extensions/mod_hjson.adoc +++ b/content/documentation/extensions/mod_hjson.adoc @@ -28,7 +28,7 @@ suited for humans: --- Hereby the hierarchical structure of the JSON document will be mapped to a -corresponding `PropertyValue` tree structure. This strucuture can be mapped +corresponding `PropertyValue` tree structure. This structure can be mapped to flat key-value pairs of type `String`, e.g. the above will be mapped to [source, properties] diff --git a/content/documentation/extensions/mod_json.adoc b/content/documentation/extensions/mod_json.adoc index 3d7c7d5..cb4220a 100644 --- a/content/documentation/extensions/mod_json.adoc +++ b/content/documentation/extensions/mod_json.adoc @@ -25,7 +25,7 @@ Tamaya _JSON_ provides support for reading configuration in JSON (Java Serialize --- Hereby the hierarchical structure of the JSON document will be mapped to a -corresponding `PropertyValue` tree structure. This strucuture can be mapped +corresponding `PropertyValue` tree structure. This structure can be mapped to flat key-value pairs of type `String`, e.g. the above will be mapped to [source, properties]
[incubator-tamaya-site] 01/08: Fix typos in HOCON doc
This is an automated email from the ASF dual-hosted git repository. pottlinger pushed a commit to branch vote-0.4-incubating-01 in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git commit c52252e377f88b963044bd073b2901822a3aeb94 Author: Hugo Hirsch AuthorDate: Tue Aug 27 22:59:46 2019 +0200 Fix typos in HOCON doc --- content/documentation/extensions/mod_hocon.adoc | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/documentation/extensions/mod_hocon.adoc b/content/documentation/extensions/mod_hocon.adoc index 15aa87e..3808b3d 100644 --- a/content/documentation/extensions/mod_hocon.adoc +++ b/content/documentation/extensions/mod_hocon.adoc @@ -7,12 +7,12 @@ toc::[] [[JSON]] -== Tamaya JSON (Extension Module) -Tamaya _JSON_ is an extension module. Refer also to the link:../extensions.html[extensions documentation] for further details. +== Tamaya HOCON (Extension Module) +Tamaya _HOCON_ is an extension module. Refer also to the link:../extensions.html[extensions documentation] for further details. -=== What functionality this module provides ? +=== What functionality does this module provide? -Tamaya _HOCON_ provides support for reading configuration using Human Optimized Configuration) HOCON +Tamaya _HOCON_ provides support for reading configuration using Human Optimized Configuration (HOCON) format as defined by http://https://lightbend.github.io/config/[Lightbend Typesafe Config]: [source, hcon] @@ -29,7 +29,7 @@ format as defined by http://https://lightbend.github.io/config/[Lightbend Typesa Hereby the hierarchical structure of the HOCON document will be mapped into an according `PropertyValue` tree structure. By default this structure can be -mapped to flat key-value pairs of type `String`, e.g. the bove will be mapped to +mapped to flat key-value pairs of type `String`, e.g. the above will be mapped to [source, properties] --- @@ -49,7 +49,7 @@ The module is based on Java 8. === Installation -To use the JSON extension module you only must add the corresponding dependency to your module: +To use the HOCON extension module you only must add the corresponding dependency to your module: [source, xml] ---
[incubator-tamaya-site] 05/08: Harmonize OSGi
This is an automated email from the ASF dual-hosted git repository.
pottlinger pushed a commit to branch vote-0.4-incubating-01
in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git
commit 47eb70635786a4e66653ceb35fe7648e561e5acb
Author: Hugo Hirsch
AuthorDate: Tue Aug 27 23:09:51 2019 +0200
Harmonize OSGi
---
content/documentation/extensions/mod_osgi.adoc | 182 -
1 file changed, 91 insertions(+), 91 deletions(-)
diff --git a/content/documentation/extensions/mod_osgi.adoc
b/content/documentation/extensions/mod_osgi.adoc
index 14f833a..7384b4d 100644
--- a/content/documentation/extensions/mod_osgi.adoc
+++ b/content/documentation/extensions/mod_osgi.adoc
@@ -1,20 +1,20 @@
:jbake-type: page
:jbake-status: published
-= Apache Tamaya - Extensions: OSGI Integration
+= Apache Tamaya - Extensions: OSGi Integration
toc::[]
-[[OSGI]]
-== Tamaya OSGI Support
+[[OSGi]]
+== Tamaya OSGi Support
-Tamaya _OSGI_ is an extension module. Refer to the
link:../extensions.html[extensions documentation] for further details.
+Tamaya _OSGi_ is an extension module. Refer to the
link:../extensions.html[extensions documentation] for further details.
=== What functionality this module provides ?
-Tamaya _OSGI_ provides support for integration with OSGI. Hereby Tamaya does
actively override or extend the OSGI
+Tamaya _OSGi_ provides support for integration with OSGi. Hereby Tamaya does
actively override or extend the OSGi
+ConfigAdmin+ based configuration with entries stored and managed by Tamaya.
Tamaya provides also shell extensions
to enable/perform configuration loading and restoring actions.
Optionally Tamaya also provides extension for automatically trigger
configuration updates, when configuration has
@@ -24,8 +24,8 @@ been changed and configuration injection using Tamaya's
injection API.
=== Compatibility
All module described are based on Java 8, so it will run on Java 8 and beyond.
-The modules are built against *OSGI Compendium version 5.0*. Tamaya OSGI
support
-is tested against the following OSGI runtimes:
+The modules are built against *OSGi Compendium version 5.0*. Tamaya OSGi
support
+is tested against the following OSGi runtimes:
* Apache Karaf, version 4.0.7
* Apache Felix, version 5.6.1
@@ -34,12 +34,12 @@ is tested against the following OSGI runtimes:
=== Installation
-To benefit from Tamaya in an OSGI context you must deploy at least the
following modules to
-your OSGI runtime environment:
+To benefit from Tamaya in an OSGi context you must deploy at least the
following modules to
+your OSGi runtime environment:
[source, listing, subs=attributes+]
---
-# Runtime with OSGI ConfigAdmin support, e.g.
+# Runtime with OSGi ConfigAdmin support, e.g.
org.apache.felix:org.apache.felix.configadmin:{felix_version}
# API and core
org.apache.geronimo.specs:geronimo-annotation_1.2_spec:1.0
@@ -52,38 +52,38 @@ org.apache.tamaya.ext:tamaya-osgi:{tamaya_version}
---
-=== Tamaya Service Loading in OSGI
+=== Tamaya Service Loading in OSGi
-Important to know is that within OSGI class- and resource loading is not
compatible with standard Java SE. Also
-in OSGI, bundles can be loaded or unloaded at any time, so Tamaya's logic must
cope with this as well.
+Important to know is that within OSGi class- and resource loading is not
compatible with standard Java SE. Also
+in OSGi, bundles can be loaded or unloaded at any time, so Tamaya's logic must
cope with this as well.
These constraints are handled by Tamaya (implemented in +tamaya-core+ and
+tamaya-osgi+) as follows:
-* Tamaya registers a +OSGIServiceContext+ which reads all
+java.util.ServiceLoader+ configurations and
- registers them as OSGI services. Hereby integration is two-way: The core
module contains an
- OSGI +Activator+ that replaces Tamaya's default +ServiceContext+ with an
OSGI based implementation that
- will consume all services from the OSGI service API. Consequently you can
also register Tamaya extensions
- as OSGI services using standard OSGI tooling (e.g. your own +PropertySource+
instances). Tamaya hereby
- also does not store any service references, so the dynamic nature of OSGI is
fully honored.
+* Tamaya registers a +OSGiServiceContext+ which reads all
+java.util.ServiceLoader+ configurations and
+ registers them as OSGi services. Hereby integration is two-way: The core
module contains an
+ OSGi +Activator+ that replaces Tamaya's default +ServiceContext+ with an
OSGi based implementation that
+ will consume all services from the OSGi service API. Consequently you can
also register Tamaya extensions
+ as OSGi services using standard OSGi tooling (e.g. your own +PropertySource+
instances). Tamaya hereby
+ also does not store any service references, so the dynamic nature of OSGi is
fully honored.
* Tamaya's +ServiceContext+ SPI does a
[incubator-tamaya-site] branch vote-0.4-incubating-01 updated (9f67331 -> 2a2931f)
This is an automated email from the ASF dual-hosted git repository. pottlinger pushed a change to branch vote-0.4-incubating-01 in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git. from 9f67331 TAMAYA-398 TAMAYA-399 TAMAYA-400 TAMAYA-401 TAMAYA-402 TAMAYA-403 TAMAYA-404 TAMAYA-405 TAMAYA-406 TAMAYA-407 Added/updated docs. new c52252e Fix typos in HOCON doc new fc17976 Fix typos in JSON doc new 1e73bd2 Fix typos in docs new 8e59f81 Fix Tamaya as Standards, harmonize OSGi new 47eb706 Harmonize OSGi new 7f5b8b0 Harmonize OSGi new aa384b4 Harmonze OSGi, but not in methods new 2a2931f Harmonze OSGi The 8 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/development/possible-contributions.adoc| 4 +- content/documentation/api.adoc | 8 +- content/documentation/core.adoc| 2 +- content/documentation/extensions.adoc | 2 +- content/documentation/extensions/mod_cdi.adoc | 2 +- content/documentation/extensions/mod_features.adoc | 2 +- content/documentation/extensions/mod_hjson.adoc| 2 +- content/documentation/extensions/mod_hocon.adoc| 12 +- .../documentation/extensions/mod_injection.adoc| 2 +- content/documentation/extensions/mod_json.adoc | 8 +- content/documentation/extensions/mod_osgi.adoc | 182 ++--- .../documentation/extensions/mod_usagetracker.adoc | 2 +- content/documentation/usecases.adoc| 2 +- content/highleveldesign.adoc | 4 +- content/tamayaasastandard.adoc | 21 ++- 15 files changed, 127 insertions(+), 128 deletions(-)
[incubator-tamaya-site] 07/08: Harmonze OSGi, but not in methods
This is an automated email from the ASF dual-hosted git repository.
pottlinger pushed a commit to branch vote-0.4-incubating-01
in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git
commit aa384b473af35f650064eebb3d7ffc10955432b5
Author: Hugo Hirsch
AuthorDate: Tue Aug 27 23:16:54 2019 +0200
Harmonze OSGi, but not in methods
---
content/documentation/extensions/mod_features.adoc | 4 ++--
content/documentation/extensions/mod_osgi.adoc | 14 +++---
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/content/documentation/extensions/mod_features.adoc
b/content/documentation/extensions/mod_features.adoc
index e51c603..bc55ae8 100644
--- a/content/documentation/extensions/mod_features.adoc
+++ b/content/documentation/extensions/mod_features.adoc
@@ -62,7 +62,7 @@ public final class Features {
public static boolean extSpringCoreAvailable();
public static boolean extJndiAvailable();
-public static boolean extOSGiAvailable();
+public static boolean extOSGIAvailable();
public static boolean checkClassIsLoadable(String classname);
}
@@ -83,5 +83,5 @@ public final class Features {
* +jndiAvailable();+ checks for the link:mod_jndi.html[_tamaya_jndi_] module.
* +extJndiAvailable();+ checks if creation of a new `InitialContext` is
successful.
* +extSpringCoreAvailable();+ checks if Spring Core is on the classpath.
-* +extOSGiAvailable();+ checks the OSGi framework is on the classpath.
+* +extOSGIAvailable();+ checks the OSGi framework is on the classpath.
* Finally +checkClassIsLoaded(String)+ tries to load a class. If it fails,
`false` is returned.
diff --git a/content/documentation/extensions/mod_osgi.adoc
b/content/documentation/extensions/mod_osgi.adoc
index 7384b4d..6d75a1a 100644
--- a/content/documentation/extensions/mod_osgi.adoc
+++ b/content/documentation/extensions/mod_osgi.adoc
@@ -58,7 +58,7 @@ Important to know is that within OSGi class- and resource
loading is not compati
in OSGi, bundles can be loaded or unloaded at any time, so Tamaya's logic must
cope with this as well.
These constraints are handled by Tamaya (implemented in +tamaya-core+ and
+tamaya-osgi+) as follows:
-* Tamaya registers a +OSGiServiceContext+ which reads all
+java.util.ServiceLoader+ configurations and
+* Tamaya registers a +OSGIServiceContext+ which reads all
+java.util.ServiceLoader+ configurations and
registers them as OSGi services. Hereby integration is two-way: The core
module contains an
OSGi +Activator+ that replaces Tamaya's default +ServiceContext+ with an
OSGi based implementation that
will consume all services from the OSGi service API. Consequently you can
also register Tamaya extensions
@@ -415,7 +415,7 @@ public interface TamayaConfigService{
* @param section a subsection to be filter (using startsWith).
* @return the (optionally filtered) OSGi configuration.
*/
-Dictionary getOSGiConfiguration(String pid, String section);
+Dictionary getOSGIConfiguration(String pid, String section);
/**
* Checks if a backup exists.
@@ -522,7 +522,7 @@ public interface ConfigInjectionService {
T configure(Bundle bundle, T instance);
/**
- * Creates a suzpplier, which supplies events as created by the basic
supplier, which are
+ * Creates a supplier, which supplies events as created by the basic
supplier, which are
* automatically configured, when supplying.
* @param supplier the base supplier, not null.
* @param bundle the target bundle, not null.
@@ -588,7 +588,7 @@ tamaya:tm_backup_create [options] pid
+++
| +tm_backup_delete+
-| Deletes the OSGi configuration backup of Tamya.
+| Deletes the OSGi configuration backup of Tamaya.
| +++
SYNTAX
@@ -599,7 +599,7 @@ tamaya:tm_backup_delete pid
+++
| +tm_backup_list+
-| List the backed-up OSGi configuration before Tamya applied changes.
+| List the backed-up OSGi configuration before Tamaya applied changes.
| +++
SYNTAX
@@ -610,7 +610,7 @@ tamaya:tm_backup_list [pid]
+++
| +tm_backup_restore+
-| Restores the OSGi configuration backup of Tamya and disabled the PID for
Tamaya configuration.
+| Restores the OSGi configuration backup of Tamaya and disabled the PID for
Tamaya configuration.
| +++
SYNTAX
@@ -707,7 +707,7 @@ tamaya:tm_history_maxsize_set size
+++
| +tm_info+
-| Show he current Tamaya status.
+| Show the current Tamaya status.
| +++
SYNTAX
[incubator-tamaya-site] 08/08: Harmonze OSGi
This is an automated email from the ASF dual-hosted git repository.
pottlinger pushed a commit to branch vote-0.4-incubating-01
in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git
commit 2a2931f780a41d39ac42fcfc28b24ab68cd37c8b
Author: Hugo Hirsch
AuthorDate: Tue Aug 27 23:19:25 2019 +0200
Harmonze OSGi
---
content/development/possible-contributions.adoc | 4 ++--
content/documentation/api.adoc | 8
content/documentation/core.adoc | 2 +-
content/documentation/extensions.adoc | 2 +-
content/documentation/usecases.adoc | 2 +-
content/highleveldesign.adoc| 4 ++--
6 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/content/development/possible-contributions.adoc
b/content/development/possible-contributions.adoc
index 60503ef..0149504 100644
--- a/content/development/possible-contributions.adoc
+++ b/content/development/possible-contributions.adoc
@@ -16,7 +16,7 @@ toc::[]
{name} is the Apache standard for flexible and powerful configuration.
Objective is to provide flavors for
Java SE, ME as well as to ship with powerful features for Java EE and Cloud
Solutions. All functions provided
is build on top of a small but very powerful, flexible and extendible API.
This API is implemented by a core implementation,
-which then can be extended or adapted for use in different runtime scenarios,
such as SE, ME, EE, Spring, OSGI
+which then can be extended or adapted for use in different runtime scenarios,
such as SE, ME, EE, Spring, OSGi
and more. Similarly additional modules may be provided that help also existing
solution to be plugged into
{name}, so you can start right away using {name} without having to
rebuild/change your existing application.
@@ -108,7 +108,7 @@ storing/retreiving/managing configuration:
=== Integration with Jigsaw
-Once Jigsaw is mature and in a usable (still early) stage, examples are to be
created and tested, where OSGI is used as
+Once Jigsaw is mature and in a usable (still early) stage, examples are to be
created and tested, where OSGi is used as
the basic runtime platform, e.g. Apache Felix, but as well others.
== Distributed/Remote Configuration Support
diff --git a/content/documentation/api.adoc b/content/documentation/api.adoc
index 0f975b3..29957a5 100644
--- a/content/documentation/api.adoc
+++ b/content/documentation/api.adoc
@@ -62,7 +62,7 @@ The API provides the artifacts as described in the
link:../highleveldesign.html[
+ConfigurationContextBuilder+. This builder can be obtained calling
+Configuration.createConfigurationBuilder();+.
** Finally +ServiceContext+ and +ServiceContextManager+ provide an
abstraction to the underlying runtime environment,
allowing different component loading and lifecycle strategies to be used.
This is very useful since component (service)
- loading in Java SE, Java EE, OSGI and other runtime environments may be
differ significantly. In most cases even
+ loading in Java SE, Java EE, OSGi and other runtime environments may be
differ significantly. In most cases even
extension programmers will not have to deal with these internals.
@@ -746,7 +746,7 @@ builder.addPropertySourceProvider(new
MyPropertySourceProvider());
== The ServiceContext
The +ServiceContext+ allows to define how components are loaded in Tamaya. It
is the glue layer, which interacts
-with the underlying runtime system such as Java SE, Java EE, OSGI, VertX etc.
+with the underlying runtime system such as Java SE, Java EE, OSGi, VertX etc.
The +ServiceContext+ hereby defines access methods to obtain components,
whereas itself it is available from the
+ServiceContextManager+ singleton:
@@ -788,7 +788,7 @@ With the +ServiceContext+ a component can be accessed in
two different ways:
. the _register_ methods allow to explcitly register (and optionally override)
a service or services
registered.
. Finally the methods `getResource(s)` allow to load resources from the
classpath. This is especially useful
- when running in an OSGI context, where loading of resources from the
classloaders will fail.
+ when running in an OSGi context, where loading of resources from the
classloaders will fail.
## Examples
@@ -885,5 +885,5 @@ Furthermore Tamaya also implements or supports:
* the API as defined by JSR 310 (Config JSR)
* the Microprofile API
* the Spring Configuration Mechanism
-* integration with the OSGI `ConfigAdmin` API.
+* integration with the OSGi `ConfigAdmin` API.
* the Apache Camel Configuration SPI
diff --git a/content/documentation/core.adoc b/content/documentation/core.adoc
index 197a556..d67cb2b 100644
--- a/content/documentation/core.adoc
+++ b/content/documentation/core.adoc
@@ -11,7 +11,7 @@ and building blocks for supporting SPI implementations.
Tamaya Core contains the following artifacts:
* A service loader implementation, configurations and further logic
[incubator-tamaya-site] branch vote-0.4-incubating-01 updated: TAMAYA-398 TAMAYA-399 TAMAYA-400 TAMAYA-401 TAMAYA-402 TAMAYA-403 TAMAYA-404 TAMAYA-405 TAMAYA-406 TAMAYA-407 Added/updated docs.
This is an automated email from the ASF dual-hosted git repository. pottlinger pushed a commit to branch vote-0.4-incubating-01 in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git The following commit(s) were added to refs/heads/vote-0.4-incubating-01 by this push: new 9f67331 TAMAYA-398 TAMAYA-399 TAMAYA-400 TAMAYA-401 TAMAYA-402 TAMAYA-403 TAMAYA-404 TAMAYA-405 TAMAYA-406 TAMAYA-407 Added/updated docs. 9f67331 is described below commit 9f673319a67489973dfad4fff4ec189855239a57 Author: Hugo Hirsch AuthorDate: Tue Aug 27 22:54:49 2019 +0200 TAMAYA-398 TAMAYA-399 TAMAYA-400 TAMAYA-401 TAMAYA-402 TAMAYA-403 TAMAYA-404 TAMAYA-405 TAMAYA-406 TAMAYA-407 Added/updated docs. --- content/documentation/extensions/mod_hjson.adoc | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/documentation/extensions/mod_hjson.adoc b/content/documentation/extensions/mod_hjson.adoc index 6ff79ce..96a37cf 100644 --- a/content/documentation/extensions/mod_hjson.adoc +++ b/content/documentation/extensions/mod_hjson.adoc @@ -10,7 +10,7 @@ toc::[] == Tamaya HJSON (Extension Module) Tamaya _HJSON_ is an extension module. Refer also to the link:../extensions.html[extensions documentation] for further details. -=== What functionality this module provides ? +=== What functionality does this module provide? Tamaya _HJSON_ provides support for reading configuration in HJSON, a JSP similar format better suited for humans: @@ -29,7 +29,7 @@ suited for humans: Hereby the hierarchical structure of the JSON document will be mapped to a corresponding `PropertyValue` tree structure. This strucuture can be mapped -to flat key-value pairs of type `String`, e.g. the bove will be mapped to +to flat key-value pairs of type `String`, e.g. the above will be mapped to [source, properties] --- @@ -49,7 +49,7 @@ The module is based on Java 8. === Installation -To use the HJSON extension module you only must add the corresponding dependency to your module: +To use the HJSON extension module you only must add the corresponding dependency to your project: [source, xml] --- @@ -65,7 +65,7 @@ This extension also transitively requires the +tamaya.formats+ module. === Reading configuration in HJSON -For reading HJSON based onfiguration most easily a +HJSONFormat+ can be +For reading HJSON based configuration most easily a +HJSONFormat+ can be used: [source, java]
svn commit: r35393 - in /dev/incubator/tamaya/0.4-incubating: ./ apiandcore/ extensions/ keys/
Author: anatole Date: Tue Aug 27 07:10:30 2019 New Revision: 35393 Log: TAMAYA-408 Preparing release. Added: dev/incubator/tamaya/0.4-incubating/ dev/incubator/tamaya/0.4-incubating/DISCLAIMER dev/incubator/tamaya/0.4-incubating/LICENSE dev/incubator/tamaya/0.4-incubating/NOTICE dev/incubator/tamaya/0.4-incubating/apiandcore/ dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.tar.gz (with props) dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.tar.gz.asc dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.zip (with props) dev/incubator/tamaya/0.4-incubating/apiandcore/apache-tamaya-distribution-0.4-incubating-src.zip.asc dev/incubator/tamaya/0.4-incubating/extensions/ dev/incubator/tamaya/0.4-incubating/extensions/apache-tamaya-extension-distribution-0.4-incubating-src.tar.gz (with props) dev/incubator/tamaya/0.4-incubating/extensions/apache-tamaya-extension-distribution-0.4-incubating-src.tar.gz.asc dev/incubator/tamaya/0.4-incubating/extensions/apache-tamaya-extension-distribution-0.4-incubating-src.zip (with props) dev/incubator/tamaya/0.4-incubating/extensions/apache-tamaya-extension-distribution-0.4-incubating-src.zip.asc dev/incubator/tamaya/0.4-incubating/keys/ dev/incubator/tamaya/0.4-incubating/keys/KEYS Added: dev/incubator/tamaya/0.4-incubating/DISCLAIMER == --- dev/incubator/tamaya/0.4-incubating/DISCLAIMER (added) +++ dev/incubator/tamaya/0.4-incubating/DISCLAIMER Tue Aug 27 07:10:30 2019 @@ -0,0 +1,10 @@ +Apache Tamaya is an effort undergoing incubation at The Apache Software +Foundation (ASF), sponsored by Apache Incubator PMC. + +Incubation is required of all newly accepted projects until a further review +indicates that the infrastructure, communications, and decision making process +have stabilized in a manner consistent with other successful ASF projects. + +While incubation status is not necessarily a reflection of the completeness +or stability of the code, it does indicate that the project has yet to be +fully endorsed by the ASF. \ No newline at end of file Added: dev/incubator/tamaya/0.4-incubating/LICENSE == --- dev/incubator/tamaya/0.4-incubating/LICENSE (added) +++ dev/incubator/tamaya/0.4-incubating/LICENSE Tue Aug 27 07:10:30 2019 @@ -0,0 +1,202 @@ +Apache License + Version 2.0, January 2004 +http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall m
