On Thu, Jul 26, 2012 at 4:26 AM, Gary Kopp <gary(a)roksw.com> wrote: I usually only open what I'm working on in Eclipse because otherwise with commons/rendering/platform it's a lot of projects and it's slowing down everything for things you probably don't care. As for the missing mapping between Maven plugins and m2e handlers: * aspectJ-maven-plugin: could not find any either, there used to be one but it does not work anymore on 4.x. There is no official version of AJDT for 4.x so that's probably why it's not yet fixed but it

should be quickly fixed as soon as there is an official AJDT for 4.x. In that case it's not very hard to setup AJDT yourself properly for the project, basically it's just about enabling it for the project and adding the right folder in the list of source folders if I remember well. But aspectj is used only in some legacy projects to produce retro-compatibility APIs so you are probably not going to need it very often. * maven-antrun-plugin: used for a hack in one of the legacy projects so for now it should not be a big deal for you * maven-remote-resources-plugin: not sure why you have issue with this one, m2e ignore it by default and just indicate it in a warning -- Thomas Mortagne

Thomas, On a minor note, I guess I could "solve" the aspect plugin problem by falling back to Indigo. And perhaps solve the other two problems by not importing the two projects that are involved -- xwiki-commons-component-legacy-default and xwiki-commons-tool-license-resources, although this might result in a non-buildable project tree in Eclipse anyway. On a more significant note, what I intended to do may be infeasible. And possibly never attempted. My goal is to study virtually every part of the code base. With Eclipse I could easily follow class and method references in as much depth as I wanted. And I could theoretically use container-based debugging to trace execution flow through the entire application. But all of that requires that I have the entire code base in one Eclipse workspace, and that's what I was starting out to build. Would that be hopeless/fruitless? I do have alternatives to Eclipse for at least part of my goal, but not for real-time debugging.

-----Original Message----- From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] On Behalf Of Thomas Mortagne Sent: Thursday, July 26, 2012 3:25 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons On Thu, Jul 26, 2012 at 12:23 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com> wrote: Actually there is one now since 4.2 (there was not not very long ago) so I guess (hope) the handler is probably going to be fixed in not too long. > should be quickly fixed as soon as there is an official AJDT for 4.x. > In that case it's not very hard to setup AJDT yourself properly for > the project, basically it's just about enabling it for the project and > adding the right folder in the list of source folders if I remember > well. But aspectj is used only in some legacy projects to produce > retro-compatibility APIs so you are probably not going to need it very > often. > * maven-antrun-plugin: used for a hack in one of the legacy projects > so for now it should not be a big deal for you > * maven-remote-resources-plugin: not sure why you have issue with this > one, m2e ignore it by default and just indicate it in a warning

I do use m2e and it's working great for me. For me having to regenerate everytime you modify a pom is a pain. On Thu, Jul 26, 2012 at 2:28 PM, Gary Kopp <gary(a)roksw.com> wrote: -- Thomas Mortagne

Fabio, Thanks for adding your two cents. I had seen Thomas' doc on debugging under Eclipse and it attracted me. Now I'm thinking I need to combine your/Thomas approach, using m2eclipse, with Sergiu's approach of using Maven's eclipse:eclipse without m2eclipse. Then I can go in any direction -- browse the entire codebase following all references _or_ debug one or more specific modules. All I really have to do to make this practical is maintain two separate clones of the Git code base (since they will have different Eclipse project metadata created within them). --Gary -----Original Message----- From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] On Behalf Of Fabio Mancinelli Sent: Thursday, July 26, 2012 6:03 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons 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: _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Fabio, The potential problem with relying on m2eclipse exclusively is that I have found that some XWiki Maven projects won't import correctly. That's what started this thread. But, those errors would seem to be the exception rather than the rule and may be irrelevant for my purposes. So, I'll go with the m2e approach for now.

xwiki-debug-eclipse (and lately also on jetty). Works out-of-the-box, just define a profile and go. Are you talking about a new Maven profile?

Thanks for your help. --Gary -----Original Message----- From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] On Behalf Of Fabio Mancinelli Sent: Thursday, July 26, 2012 7:32 AM To: XWiki Developers Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons Hmmm. Frankly I see the two approaches as mutually exclusive. If you import projects using m2e and it works, it doesn't make sense to use the other approach because you will already have all that is provided by the other one (and even more) You are able to browse the the entire code base with both of the approaches (just import anything you need, and if you don't use snapshots m2e will download source code artifacts automatically and show you the code for the dependencies if you don't have it available) I still think that the M2E + wiki-debug-eclipse is a superior approach (when it works fine :)) -Fabio P.S.: Re another mail you sent, I usually deploy on tomcat with xwiki-debug-eclipse (and lately also on jetty). Works out-of-the-box, just define a profile and go. On Thu, Jul 26, 2012 at 2:21 PM, Gary Kopp <gary(a)roksw.com> wrote: them). _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Fabio, Thanks for adding your two cents. I had seen Thomas' doc on debugging under Eclipse and it attracted me. Now I'm thinking I need to combine your/Thomas approach, using m2eclipse, with Sergiu's approach of using Maven's eclipse:eclipse without m2eclipse. Then I can go in any direction -- browse the entire codebase following all references _or_ debug one or more specific modules. All I really have to do to make this practical is maintain two separate clones of the Git code base (since they will have different Eclipse project metadata created within