[
https://issues.apache.org/jira/browse/TAMAYA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Ottlinger reopened TAMAYA-139:
--------------------------------------
Thanks for your patch - since I ran into multiple problems with the "load from
classpath" approach at work I'd recommend to rename server-version.properties
to something more fully qualified such as
{code}
tamaya-server.properties
{code}
to not introduce clashes with arbitrary other components that try to load a
server-version file.
Personall I'm in favour of the static generation approach since it does not
open an attack vector in contrast to loading via classpath, but I'm okay with
your proposal, Oliver.
> Integrate maven version of Tamaya into JSON being exposed in its
> implementation
> -------------------------------------------------------------------------------
>
> Key: TAMAYA-139
> URL: https://issues.apache.org/jira/browse/TAMAYA-139
> Project: Tamaya
> Issue Type: Improvement
> Affects Versions: 0.2-incubating
> Reporter: Philipp Ottlinger
> Assignee: Oliver B. Fischer
> Priority: Minor
> Fix For: 0.2-incubating
>
>
> While working on TAMAYA-134 I stumbled upon
> {code}
> org.apache.tamaya.server.ConfigurationResource
> {code}
> containing the following JSON snippet in its
> version():
> {code}
> "{ \"version\" : \"Apache Tamaya: 0.2-incubating\" }"
> {code}.
> This information should be calculated depending on mvn version information.
> One way is to generate a class with maven-resource-plugin that contains the
> version such as:
> {code}
> class Version {
> private String version = "${project.version}";
> public String getVersion() {
> return version;
> }
> }
> {code}
> This class can be used in a static matter in this endpoint.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
