Jorg Heymans skrev:
Jorg Heymans wrote:
Anyhow, there seems to be something not quite right yet with our eclipse
setup. If you run eclipse:eclipse from the top level pom in
whiteboard/cocoon-flat-layout, you'll see that the plugin generates
eclipse project dependencies between the different modules (very
useful!) . For some reason, it's not doing this in trunk. I'm currently
investigating this ...
The trick here is to do
$mvn clean install eclipse:clean eclipse:eclipse
before importing the project. The plugin seems to need the projects to
be *installed* before it will generate eclipse project references from a
reactor build.
I tried it and it worked.
Now i'm not sure if this really speeds up the development cycle , but
having our modules depend on each other as eclipse projects is another
step in the right direction I hope.
Absolutely! When you work at several blocks at once it is important. And
it also give you connection to the latest source, when you get to e.g.
core during debuging.
/Daniel
