[ http://jira.magnolia.info/browse/MAGNOLIA-1440?page=comments#action_13768 ] Philipp Bracher commented on MAGNOLIA-1440: -------------------------------------------
I would like to change this as such: - update of a (minor) version should not install/bootstrap all files again (might overwrite custom settings) - additional onUpdate() method - list changed (bootsrap) files (maybe in the modules descriptor) - in case magnolia.develop property is set the redeploy thread is running (no additional triggering after each start) - the deploy util checks the modification date and checks jsps more often (since this is what you need most) > redeployment util allows module to clobber other modules installed files. > ------------------------------------------------------------------------- > > Key: MAGNOLIA-1440 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1440 > Project: Magnolia > Issue Type: Bug > Reporter: Chris Miner > Assigned To: Boris Kraft > > When a module is updated, part of the module registration process involves > installing files. Only files under mgnl-files containing the module name as > part of the path are installed. This is a good thing since it means each > module has its own file 'name space'. > However if you trigger redeployment via the deployment utils page, no such > check is used. Any file anywhere in the classpath under mgnl-files is > unpacked and written to the file system. > You might notice this if your jsps never deploy by themselves and you find > yourself having to deploy them manually every time you update your modules > version number. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
