On Thu, Jul 26, 2012 at 3:49 PM, Gary Kopp <[email protected]> wrote: > 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. > Yep I know, that's why I said "if it works" in my previous message :)
>>> 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. > > Are you talking about a new Maven profile? > No, WTP profile (File -> New -> Other -> Server) -Fabio > Thanks for your help. > > --Gary > > -----Original Message----- > From: [email protected] [mailto:[email protected]] 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 <[email protected]> wrote: >> 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: [email protected] [mailto:[email protected]] 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 <[email protected]> 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 >>> [email protected] >>> http://lists.xwiki.org/mailman/listinfo/devs >> _______________________________________________ >> devs mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/devs >> >> _______________________________________________ >> devs mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
