Hello Fabio, Le 29 oct. 2012 à 10:22, Fabio Mancinelli a écrit :
> Paul, I know that Maven does it :) you bet! > My goal is just to have a very automated workflow *within* the IDE, > that takes the least time from a source modification to an > up=and-running XWiki incorporating that modification. My fear there, at least of previous eras of such IDE integration is that some day you get a decoupling between what maven (or anything command-line) does and what the IDE does. Then you're in trouble. It seems to be not your case currently, so that is good. > With xwiki-debug-* you modify a .java source, you click a button and > you're done (no round-trips to the shell, double-checks, or whatever) > And IntelliJ looks to be also blazing fast wrt Eclipse. This workflow > takes less than 20 secs on my laptop (including XWiki startup time). The advantage of the remote setup is precisely that I can outsource my XWiki (curriki's basis is a bit bigger than xwiki's basis!) to a server, at home I have my little server for this but the debug and edit is still on the laptop. 20 second is really good indeed! > Btw, I am curious to know what is your development workflow. What do > you do if you want to change something in, let's say, the > xwiki-rest-server module? > Maybe we can improve even more. When changing any source, I generally deploy and run, build inside IntelliJ, connect with remote debug, then do the extra modification and compile the given file, this requests the hot-swap and takes a few seconds only. This fails for API changes however (but since CLIRR will hit me later on, I'd better be warned ;-)). I'm pretty sure that also works in your case as well. For a change of a resource, I need to copy manually (no filtering then), then re-run the view. This very fast and effective but it needs three apps (IDE, terminal, browser) instead of two. paul _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
