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 first, then run eclipse:eclipse, then import it into eclipse.
- Joakim
nicolas de loof wrote:
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]
[INFO] Failed to resolve artifact.
Missing:
--
1)
org.apache.maven.archiva:archiva-database-consumers:jar:1.0-alpha-1-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file
-DgroupId=org.apache.maven.archiva-DartifactId=archiva-database-consumers
\
-Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Path to dependency:
1)
org.apache.maven.archiva:archiva-webapp:war:1.0-alpha-1-SNAPSHOT
2)
org.apache.maven.archiva:archiva-scheduled:jar:1.0-alpha-1-SNAPSHOT
3)
org.apache.maven.archiva:archiva-database-consumers:jar:1.0-alpha-1-SNAPSHOT
...
I can't import all modules in Eclipse before mvn install is successfull.
This may create issues if the code in SVN has compilation failures due to
some unfortunate commit.
2007/5/3, Andrew Williams <[EMAIL PROTECTED]>:
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 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.
