26 Jul
2012
26 Jul
'12
1:19 p.m.
On 07/26/2012 07:08 AM, Gary Kopp wrote:
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.
What works for me is to skip m2eclipse completely. I use Eclipse for
browsing the code, and command line tools (git, mvn) for the rest.
To prepare the eclipse projects, just use this line:
mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true
-Pci,integration-tests,legacy,hsqldb,jetty
Then you can File->Import->Existing projects into workspace to get the
projects built by maven into Eclipse. The problem is that whenever
modules change, you'll have to regenerate/reimport the modules.
-----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:
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
On Thu, Jul 26, 2012 at 4:26 AM, Gary Kopp
<gary(a)roksw.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 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
:-)
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