That's what usually caused the problem for me. My fix was usually to bootstrap maven using my new repository as the target - that seems to pick up the right dependency somewhere! :)

We should probably check if this is fixed in CVS HEAD and if not file an issue on it.

Cheers,
Brett

Moretti, Luciano (MED) wrote:
The problem might be that I'm trying to resolve problems with
downloading dependencies and wiped the local repo to ensure that
everything necessary could be gotten off the server.


I take it that I wiped out some stuff that Maven depends on that is
automatically put in the local repo on install?

Thanks,

Luciano Moretti


-- Web Developer f2 network ~ everything essential 02 8596 4437


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to