Gerd:   I found the solution. As it turns out, this is a bug in Maven. In multi-module builds where a module depends on the test artifact of another module, those test artifacts are not available in the reactor; a `mvn install` is required before the artifacts will properly resolve. See http://jira.codehaus.org/browse/MNG-2045 for details. Your options are to run `mvn install eclipse:eclipse` or to use the Eciipse M2Eclipse plugin to resolve things within the IDE rather than simply generating the configuration files. This is only an issue for those that wish to hack on the Kite codebase itself. I think most of us (the Kite developers) didn't notice this because I think we all use IntelliJ while working on Kite.   Sorry for the confusion. ... View more