On 12/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
A few hints which might help:
1. Maven 2.0.4 has a bug when it comes to resolving dependencies. If a
parent POM defines the version to 1.0 and your POM wants 1.1, the parent
wins.
Hmm, will need to think about this one.
2. Can you download the missing POM? Sometimes, Maven believes the POM
can't be downloaded because it tries to download something else from that
repository which fails and Maven blacklists it for the build. -U doesn't
help in this case. Check your log for download errors.
The poms and artifacts are in my local m2 repository.
3. Have you tried to delete your local Maven repo? Or at least the
maven-metadata-*.xml files?
No, this was a last resort.
I'm trying to build from home and see what happens there.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
