I have a multi-tiered project which I've imported into Eclipse.
There is a master build, with several component builds underneath ( webapp, model, service, unittest, etc ).
An example of an intra-project dependency is that the webapp src contains imports from the service layer. The service build creates a jar in a project lib which the webapp build puts onto the compile classpath - life is good for compilation,
testing, etc.
When I checkout the project into Eclipse I get lots of 'cannot be resolved' messages. The builds and tests work fine within Eclipse, but how can I avoid those messages on checkout?
Since the references indeed cannot be resolved until the referenced jar is built, I can happily ignore them, but is there a way to lower the noise?
