I'm in the same boat as you teknokrat - no matter what I do, it the artifact doesn't exist in the internal remote repository, maven goes to look in repo1 for it.
In addition to this, there are a few poms it simply skips looking to my internal remote repository (like all the maven plugin poms). I wish someone with more maven 2 knowledge could repair these issues. -----Original Message----- From: Thorsten Heit [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 10:01 AM To: Maven Users List Subject: Re: whats going wrong with my build? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, > No you don't understand. The files are in my local repository already. > They are not on ibiblio. I have no idea why maven insists on looking > there. This is a purely local project. Erm, yes, haven't read it (OutOfCoffeeException...) ;-) Does your repository contain the corresponding pom for your war file? AFAIK Maven checks the central repository if the pom files do not exist in your repo, therefore the warning(s)... Apart from that, what does "mvn -e -X ..." show on your console? Thorsten -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (MingW32) iD4DBQFEkBaDQvObkgCcDe0RAs0cAKDBhdqi7jrw58a96EBUZngIpPrZyACXdDwF DOJsB0cCAY0nqSOyWcCk8w== =vb1Q -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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]
