I allready use this for my corporate projects with not having this issue :
as maven knows the projects are modules from the same parent POM, it
resolves such modules dependencies as inter-project dependencies under
eclipse and DOESN'T require the project to be installed in local repo.
Some prior
The POMs in the new trunk don't set versions for dependencies on other
arhiva modules. Maven has no issue with that when running mvn install.
I tried to do the same on my project and got error :
Validation Messages:
[0] 'dependencies.dependency.version' is missing for
That's expected.
On a fresh checkout/update, the modules do not exist in the local (or
remote) repositories yet.
When you run the eclipse:eclipse goal, it tries to resolve the
dependencies, it can't as there is no information present in the
repository system for those modules.
Compile it
