Re: [Aperture-devel] Using new mavenized Aperture in the eclipse IDE

[Antoni M. <ant...@gm...>]

Paul Hübner pisze:
> Hello together,
> 
> the "old" ANT based aperture was well integrated in the eclipse IDE. I 
> have some problems using the mavenized version of aperture together and 
> well integrated in eclipse (e.g. for source browsing and searchsing).
> 
> AFAIK the way to use a Maven based java projects in eclipse is to call 
> "mvn eclipse:clean eclipse:eclipse" on the projects root folder but this 
> does not work for aperture.  Is there a different way to get the 
> mavenized aperture integrated in the eclipse ide? I would be pleased 
> about any hints.

Back in february/march I used to use the m2eclipse

http://www.sonatype.com/products/m2eclipse

>From my experience it is great, but doesn't scale well when the project
has ~ 80 modules. Every change in parent pom triggered a recomputation
of all dependencies in all projects, which took a LOONG time.

That's why I switched to the normal maven plugin for eclipse. The tricky
part is that it works best if the 'aperture' folder, i.e. the root of
the codebase is directly below the workspace folder. Then two things
happen automatically:
- the M2_REPO classpath variable is added to the workspace configuration
- other maven projects are detected and dependencies to them are
translated into eclipse project dependencies.

If the 'aperture' folder is not directly below the workspace folder then
you need one additional step, go to the workspace folder and type

mvn -Dworkspace=. eclipse:configure-workspace

Then you can import the generated projects (Import->Existing projects
into workspace) and start working.

Hope this helps

All kinds of comments welcome

Antoni Mylka
ant...@gm...