26 Jul
2012
26 Jul
'12
4:09 p.m.
Sergiu,
If you think I should never need to maintain two Git clones I might be
missing something obvious. Let's say I want to use the m2e approach for
selective debugging, and the import existing projects approach (non-m2e) for
global code browsing. If I run mvn eclipse:eclipse it will create Eclipse
metadata files in the Git projects, and this metadata is specific to the
previously done Maven command line build. If I then use m2e to attempt to
import Maven projects from the same clone the import will try to create its
own Eclipse project metadata in the Git clone, which I would think is
incompatible with the project metadata from mvn eclipse:eclipse. Or, I'm
hopelessly confused and a lost cause :-)
--Gary
-----Original Message-----
From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] On Behalf Of
Sergiu Dumitriu
Sent: Thursday, July 26, 2012 7:53 AM
To: XWiki Developers
Subject: Re: [xwiki-devs] m2eclipse and xwiki-commons
On 07/26/2012 08:21 AM, Gary Kopp 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).
You should never have to maintain two different clones.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs