I've made some test on minimalist POM hierarchy and having multi-level
parents OR setting version using dependencyManagement doesn't break the
ability to setup eclipse without having the project installed in local
repository..
You can take a look at my poms here : http://ndeloof.free.fr/temp/poms
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
You're right, I missed it.
This has a strange side effect : when I run mvn eclipse:eclipse from a fresh
checkout, all inter-modules dependencies are unresolved :
[INFO]
[ERROR] BUILD ERROR
[INFO]
---
I have not looked, but am guessing there is a dependencyManagement
section in the parent pom.
Andy
On 3 May 2007, at 11:45, nicolas de loof wrote:
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
Adding " ${project.version} " on my modules dependencies
solves this.
What maven hack is used by archiva ???
2007/5/3, nicolas de loof <[EMAIL PROTECTED]>:
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 inst
