[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Bärfuss updated MAGNOLIA-3516:
--------------------------------------
Fix Version/s: 5.0
(was: 4.4.3)
> Allow PropertyInitializer to also use system and environment properties.
> ------------------------------------------------------------------------
>
> Key: MAGNOLIA-3516
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3516
> Project: Magnolia
> Issue Type: Improvement
> Components: core
> Affects Versions: 4.3.8, 4.4.1
> Reporter: Danilo Ghirardelli
> Assignee: Ondřej Chytil
> Fix For: 5.0
>
> Attachments: MAGNOLIA-3516-env.patch, MAGNOLIA-3516-test.patch,
> magnolia-prop.patch
>
>
> Another strange system architecture required another patch to the property
> initializer. This time the problem is that all the instances in the cluster
> must be exactly the same, without the possibility to use a context param just
> like I did in the other patch. So this time I propose to add also the
> possibility to use system properties to get the configuration files correctly.
> System properties are resolved correctly inside the property file, but they
> can't be used (at the moment) to resolve the property file itself. The
> attached patch takes care of the job (it's really minimal).
> I know that the entire property initializer should be refactored, even if the
> patch is not accepted I'd just like to write another real life scenario that
> should be included in the refactoring...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
