Adding " <version>${project.version}</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 install.
I tried to do the same on my project and got error :
Validation Messages:
[0] 'dependencies.dependency.version' is missing for
com.capgemini.quickstart:quickstart-model
Reason: Failed to validate POM
I don't see any special version setting in archiva. Did I miss something ?
Nico.
