29 Oct
2012
29 Oct
'12
9:22 a.m.
On Sat, Oct 27, 2012 at 9:27 PM, Paul Libbrecht <paul(a)hoplahup.net> wrote:
Le 26 oct. 2012 à 23:44, Fabio Mancinelli a écrit :
Paul, I know that Maven does it :)
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.
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).
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.
Thanks,
Fabio
I've always used Eclipse and the
xwiki-debug-eclipse which has a nice
property: you don't have to bother to make sure that the sources you
modify (and the corresponding JARs) are available in the webapp.
Eclipse (+ m2eclipse) does it for you by automatically synching every
modification with the corresponding webapp. And, above all, it knows
when to use a JAR coming from your repo instead of the one coming from
one of your open projects.
AFAIK if you don't use this kind of automation you have to manually
copy JARs and make sure that the correct version is deployed. A very
error prone operation involving a lot of steps, and switching back and
forth from the shell.
Maven does it for me.
And it's better so since I want maven to be used to build the webapp on the
dev/beta/production servers.
But I guess your description sounds more complete.
Indeed a modification of, say, a .vm file needs me to copy that file, not a big deal.
paul
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs