[
http://mifosforge.jira.com/browse/MIFOS-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
keithwoodlock updated MIFOS-4560:
---------------------------------
Fix Version/s: Unscheduled
> Remove LookUpValueMessages.properties from userInterface module
> ---------------------------------------------------------------
>
> Key: MIFOS-4560
> URL: http://mifosforge.jira.com/browse/MIFOS-4560
> Project: mifos
> Issue Type: Task
> Components: Internationalization
> Affects Versions: Release 2.0.0
> Reporter: Udai Gupta
> Assignee: mifosdeveloperqueue
> Fix For: Unscheduled
>
>
> *Udai asked on the mailing list*
> bq. We have LookUpValueMessages.properties in two modules, is there some
> reason? Those are not synced, messageSourceBean.xml uses the one in
> userInterface module. Change it to use the one in application module.
> *Keith's reply*
> bq. while doing either login or admin area, I think this was brought in for
> re-using its properties, however then we switched to creating unique
> properties in messages.properties.
> bq. So userIntereface module may not need this anymore and should be removed
> but just be check out to see if anything obvious around login/admin is not
> working with respect to labels
> NOTE: make sure messageSourceBean.xml is updated, and key=value pair are
> synced to the application LookUpValueMessages.properties
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
