Hello. Could you share your way of working with magnolia? How do you speed things up?
Do you use bundled magnolia or as a maven artifact? Do you develop a .war or a module? Currently i'm bored with development routine. Netbeans and magnolia as maven dependency serve pretty well on template development stage - tomcat track changes to .jsp source and redploys the file. But pure java files give me pain. Forces to undeploy, recomple and deploy again. Resulting .war is about 30Mbs and it takes some time to redeploy even locally. I'd say that working on a site as a magnolia module could speed deployment up, but I have no idea how setup development environment comfortably so it would track template files on fly. Please share. Lauri. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=69ea1310-8a60-4f43-a32d-ad8d6d62511f ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
