From: Antoni Mylka <antoni.mylka@gm...> - 2009-03-10 20:22:20
I've been trying to get to grips with the mavenized Aperture. I use
the eclipse maven plugin, I checkout aperture as a plain project and
then use Import->Maven Projects.
Then I check the "separate projects for each module" checkbox. This
makes my workspace contain about 90 projects.
1. Eclipse has a limitation. In order to compile aperture, the build
uses our vocabulary and datasource maven plugins. The command-line
maven has no problems with building the plugins first and then using
those plugins to compile the rest of the modules. Unfortunately
eclipse can't do it. When you click project->clean->clean all
projects, the result will be a set of error messages that the plugins
can't be resolved.
2. The same happens after the checkout, eclipse can't compile the
checked out sources by itself.
Solution: first checkout, then type mvn install from the command line,
then refresh all modules and only then you can start doing anything
with the source.
If you have to clean everything afterwards, nothing bad should happen,
because the generated files are placed in the source folders and the
eclipse clean won't delete them, so the process above is neccessary
only on the first checkout.
Hope this will save someone some frustration ...
All kinds of comments welcome, we all have to learn to work with this,