[
http://mifosforge.jira.com/browse/MIFOS-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udai Gupta resolved MIFOS-4388.
-------------------------------
Resolution: Fixed
Scheduled For: Product
Assignee: Michael Vorburger
I think this issue is resolved, the uncaughtException.ftl doesn't have to be
under WEB-INF/freemarker.
> uncaughtException.ftl should be in src/main/webapp/WEB-INF instead of in
> src/main/resources
> -------------------------------------------------------------------------------------------
>
> Key: MIFOS-4388
> URL: http://mifosforge.jira.com/browse/MIFOS-4388
> Project: mifos
> Issue Type: Dev Task
> Components: Build and Testing
> Reporter: Michael Vorburger
> Assignee: Michael Vorburger
>
> I've noticed that
> userInterface/src/main/resources/org/mifos/ui/freemarker/core/uncaughtException.ftl
> is the only file in that directory; all other *.ftl are in
> userInterface/src/main/webapp/WEB-INF/freemarker.
> We moved the FTL in MIFOS-3925, presumably this is a merge issue or
> overlapping timing (move was done while the feature which lead to the new
> uncaughtException.ftl was developed) ?
> http://mifosforge.jira.com/secure/StudioSearch.jspa?suggest-tracking=search&quickSearch=true&query=uncaughtException.ftl
> shows a number of JIRAs involving uncaughtException.ftl.
> A (Selenium?) test verifying that uncaughtException.ftl works as intended
> should probably be written?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
