26 Jul
2012
26 Jul
'12
2:02 p.m.
I personally use the great
https://github.com/xwiki/xwiki-debug-eclipse done by Thomas.
I import this project and (modulo some initial glitches) I am able to
start a working instance of XWiki from within the Workbench.
Then I import the modules I want to work on from xwiki-platform.
M2Eclipse takes care of using the modules open in the workbench in the
XWiki web application.
So I don't need to do any jar copying or whatever. Sometimes hot code
replacement is also applicable so you don't even have to restart the
instance when you modify stuff.
Debugging works out-of-the-box.
I think that this is a very nice environment where you can manage
building/deploying/running XWiki from a single environment, with
M2Eclipse and Eclipse WTP taking care automatically of many details
(almost everything actually).
My 2 cents.
-Fabio
On Thu, Jul 26, 2012 at 3:26 AM, Gary Kopp <gary(a)roksw.com> wrote:
Hello devs,
I just finished porting my XWiki development environment from Windows 7 to
Ubuntu 12.04. I am now able to build all projects from the command line
without errors. I'm working with the master branch from Git. I have Eclipse
Juno installed with plugins that include m2eclipse (the version from the
Eclipse update site) and AJDT. I am now trying to import the entire
xwiki-commons Maven project into Eclipse. Just as happened under Windows
(which I never asked about, since I was still trying to get command line
builds to work), there are three Maven goals (plugins) in the xwiki-commons
projects that fail to map to Eclipse plugins -- aspectJ-maven-plugin,
maven-antrun-plugin, and maven-remote-resources-plugin. Can anyone give me
some hints on how to resolve these mapping problems? Googling for answers
about this hasn't yielded anything that I can understand :-)
--Gary
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs