> Front end development. There¹s no need to rebuild the war and restart tomcat > if only templates (or css, javascript, etc) have been changed.
For css development i edit the css in place in firefox. Once i've found what works i repeat it into the original source file. Is there something similar for javascript? > E.g. If only > a couple of .vm files have been modified it¹s enough to copy these out to > tomcat. This exists already and is part of http://sesat.no/debugging-velocity-templates.html That is putting -DVELOCITY_DEBUG=true -DVELOCITY_DEVELOP_BASEDIR=<paths to templates> into CATALINA_OPTS (VELOCITY_DEBUG turns off caching so it required. it is different to VELOCITY_DEBUG_ON). > Something similar for class files would also be great, since most > IDE¹s build new class files when they¹re edited. As long as your container has auto-deployment enabled, you can hit a /search/? request with the additional parameter reload=all This should clear out all instances in all SiteKeyedFactories. Meaning that skin configurations and classes are loaded from scratch by the sesat-kernel. I'm not too sure how stable the classloaders are here but i know it works with configurations files. And it would definitely be nice to have a reload=java option to clear out just the classloaders belonging to the site. See FactoryReloads.ReloadArg > A way of automating this through the IDE would be good. Mick, you might know > of good ways of achieving this in NetBeans (?). Well the maven build automatically copies the war files over for you. So you build the war project in your IDE and you'll have already deployed the war file to your container. Since it's often two projects that need to be compiled i use command line like: cd search-command-control/; mvn install; cd - cd war/; mvn install; cd - and just cycle between them. > A possible solution could be symlinks from $TOMCAT_HOME/webapp/<app> > to the different target dirs though I¹m not really sure if this is > possible due to the structure of the projects. I have successfully used this approach before. While it works it's a headache when you have multiple checkouts and wish to change between them. I find the only real wait is the tomcat restart, not the file copy time, so here the maven build copying the war files suffices. ~mck -- "It is not enough to have a good mind; the main thing is to use it well." Descartes | semb.wever.org | sesat.no | sesam.no |
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
