Hi all, If I understand correctly, by design Magnolia will only copy the files from "mgnl-files" (in a module's JAR) into the root of the web application if the module's version number changed. But while developing, that version number might not change for some time, indicated by the usual "SNAPSHOT" suffix.
How do you handle this during development? Some things I found: In Tools, Development Tools there's a manual option "Force re-extraction of a module's files". And Phillip once wrote: [1] > I have written for one project a module version handler which > extract the files on every startup if the version is a snapshot. > I should probably checkin this version handler. (As an aside: even when changing the version number, which yields "Magnolia needs to be updated", it might be good to have (parts of) the structure available BEFORE running the version handler. Like: Spring's FreeMarkerConfigurationFactory might be looking for a folder that is non-existent until Magnolia copies the files, which happens AFTER Spring starts. I assume I can fix all such issues by including an empty folder in the webapp's WAR; if not then maybe I might need to do some hacking when my module's ModuleLifecycle#start gets invoked, or my VersionHandler is instantiated, and maybe only if "magnolia.develop" is set.) Any thoughts appreciated! Arjan. [1] http://jira.magnolia-cms.com/browse/MAGNOLIA-2504?focusedCommentId=19849&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_19849 ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
