You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@syncope.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/07/30 17:05:38 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=14079349#comment-14079349 ] 

ASF subversion and git services commented on SYNCOPE-538:
---------------------------------------------------------

Commit 1614678 from [~ilgrosso] in branch 'syncope/branches/1_2_X'
[ https://svn.apache.org/r1614678 ]

[SYNCOPE-538] Global pom property added 'conf.directory' + various fixes

> 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)