Simon Kitching wrote:
On Sat, 2006-03-18 at 21:45 +0100, Rune Flobakk wrote:
Yes, that's what I hoped for, as the parent pom is located at the
default relativePath, and as I've understood I shouldn't need to define
relativePath, only the artifactId, groupId and version, but still it
doesn't seem to pick it up when compiling.
In that case, the only thing I can think of that might be wrong is:
(or the file found has group/artefact/version
values that don't match the specified parent dependency)
Are you sure that the group/artefact/version values defined in the
parent pom sitting on disk match the values that the child pom declares?
If not, then it is the "wrong" parent pom, so the repo needs to be used.
Hehe, believe me, I've checked and double-checked this. Besides, if the
group/artefact/version values aren't correct, it shouldn't find it in
the repository either, since I've done a 'mvn install' on the parent
project, and the values there are the same as in the repository pom and
directory structure?
It works when installing the parent project as mentioned, but I still
have some trouble sleeping at night :D
Rune
Thanks for your thoughts. So far I do a 'mvn install' on the parent
project, and make sure the sub projects (modules?) are installed in the
correct order to ensure proper compilation of each sub project. It works
fine.
Ah well, as long as you have a workable solution :-)
Cheers,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
