[
https://issues.apache.org/jira/browse/APEXCORE-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944489#comment-15944489
]
ASF GitHub Bot commented on APEXCORE-658:
-----------------------------------------
GitHub user tweise opened a pull request:
https://github.com/apache/apex-core/pull/499
APEXCORE-658 Enable apex. prefix for configuration keys.
@vrozov please review
The intended behavior is to support new and old prefix in parallel.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tweise/apex-core APEXCORE-658_configKeys
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-core/pull/499.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #499
----
commit 57e1e6fc7bc7f1f593343fd43e77f00e4baf166c
Author: Thomas Weise <t...@apache.org>
Date: 2017-03-28T03:54:51Z
APEXCORE-658 Enable apex. prefix for configuration keys.
----
> Replace dt. prefix with apex. for configuration keys
> ------------------------------------------------------
>
> Key: APEXCORE-658
> URL: https://issues.apache.org/jira/browse/APEXCORE-658
> Project: Apache Apex Core
> Issue Type: Task
> Reporter: Thomas Weise
> Assignee: Thomas Weise
>
> Users should be able to configure their applications with keys that use apex.
> as prefix and this is how it should be shown in examples also. It should be
> possible to make this change w/o breaking backward compatibility.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
