Return-Path: Delivered-To: apmail-maven-users-archive@www.apache.org Received: (qmail 76817 invoked from network); 11 Sep 2005 16:44:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 11 Sep 2005 16:44:52 -0000 Received: (qmail 28429 invoked by uid 500); 11 Sep 2005 16:44:47 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 28407 invoked by uid 500); 11 Sep 2005 16:44:47 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 28392 invoked by uid 99); 11 Sep 2005 16:44:47 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Sep 2005 09:44:47 -0700 X-ASF-Spam-Status: No, hits=2.3 required=10.0 tests=DATE_IN_FUTURE_12_24 X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [64.7.141.17] (HELO codehaus.org) (64.7.141.17) by apache.org (qpsmtpd/0.29) with SMTP; Sun, 11 Sep 2005 09:44:58 -0700 Received: (qmail 11121 invoked from network); 11 Sep 2005 16:45:04 -0000 Received: from cpe000d6079f82d-cm023080004191.cpe.net.cable.rogers.com (jvanzyl@24.156.143.69) by codehaus.org with SMTP; 11 Sep 2005 16:45:04 -0000 Subject: Re: [m2] how to deal with missing dependencies From: Jason van Zyl Reply-To: jason@maven.org To: Maven Users List In-Reply-To: References: Content-Type: text/plain Organization: Maven Date: Mon, 12 Sep 2005 01:15:26 -0400 Message-Id: <1126502127.5999.658.camel@CPE000d6079f82d-CM023080004191> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Sun, 2005-09-11 at 18:19 +0200, Jorg Heymans wrote: > Hi, > > It often happens that during my project build, i get missing > dependencies and the build fails with an error like : > > Path to dependency: > 1) apache-cocoon:cocoon-core:jar:2.2-SNAPSHOT > 2) excalibur-store:excalibur-store:jar:2.1 > 3) excalibur-fortress:excalibur-fortress-container-api:jar:1.2 > 4) d-haven-managed-pool:d-haven-managed-pool:jar:1.0 > > These missing dependencies seem quite random, one day they are there, > the next they are gone. Dependencies should not just come and go. Can you take a look at ibiblio and see if you are using the correct groupId and artifactId in all cases? For example looking in the repo there is no groupId of apache- cocoon but there is a cocoon groupId: http://www.ibiblio.org/maven2/cocoon/ And in there I don't see any cocoon-core artifacts in there. > Are these poms still being actively updated > perhaps ? You can see when they were last acted upon by looking in the repo: http://www.ibiblio.org/maven2/cocoon/cocoon/2.1.7/ > What can one do to make this fail a)less often and b) not so > seemingly random ? 1) Examine the repo and make sure you're using correct groupIds and artifactIds 2) Contact the project in question and see if someone is maintain the metadata and if not 3) Register any problems here: http://jira.codehaus.org/browse/MEV > I know i could just put them in my local repository manually but that > defeats the whole purpose of maven. Yes it does :-) But sometimes you have to nudge a bit to get things into the repository and correctly. > > Thanks > Jorg Heymans > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org > For additional commands, e-mail: users-help@maven.apache.org > > -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org Simplex sigillum veri. (Simplicity is the seal of truth.) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org