You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2014/08/01 13:54:39 UTC
[jira] [Commented] (SYNCOPE-538) Externalize all WAR configuration
[ https://issues.apache.org/jira/browse/SYNCOPE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082164#comment-14082164 ]
Francesco Chicchiriccò commented on SYNCOPE-538:
------------------------------------------------
Hi [~wimmelg],
you are right, I have completely forgotten to include the mail templates in the commit: I am going to re-open this issue and fix this.
I also see your point about the embedded profile, I'll fix this as well.
> Externalize all WAR configuration
> ---------------------------------
>
> Key: SYNCOPE-538
> URL: https://issues.apache.org/jira/browse/SYNCOPE-538
> Project: Syncope
> Issue Type: Improvement
> Components: console, core
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Fix For: 1.2.0, 1.3.0
>
>
> The main webapps (core and console) require several configuration files (.properties) to work properly.
> Currently such configuration files need to reside into webapps' classpath.
> Ideally it should be possible to define a configuration directory, defined via a Maven property, where all such files can be loaded from: this would allow to implement some handful deployment scenarios (e.g. deploy the same .war files either in test and production environments).
> The same idea is to apply to e-mail templates.
--
This message was sent by Atlassian JIRA
(v6.2#6252)