Return-Path: X-Original-To: apmail-maven-users-archive@www.apache.org Delivered-To: apmail-maven-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D1413EB29 for ; Mon, 11 Feb 2013 15:32:51 +0000 (UTC) Received: (qmail 71892 invoked by uid 500); 11 Feb 2013 15:32:49 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 71450 invoked by uid 500); 11 Feb 2013 15:32:40 -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 70842 invoked by uid 99); 11 Feb 2013 15:32:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2013 15:32:38 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bmathus@gmail.com designates 74.125.83.43 as permitted sender) Received: from [74.125.83.43] (HELO mail-ee0-f43.google.com) (74.125.83.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2013 15:32:32 +0000 Received: by mail-ee0-f43.google.com with SMTP id c50so3152113eek.30 for ; Mon, 11 Feb 2013 07:32:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=MYFmusRNrvJRf/lADyeGjIV4A9T1lrw18lrTBm6UCYM=; b=nwyu2bp8qoxwZT9D7ncRaySEcGhgoKmxKCONDJEL83SIqTgfPOoYghJ31delidcWex Yv/RlPqQdjW/ntmC17Svjh6CjTGqXFKPsoT+sDmFgIjPQEto+GWfiBWbLewtmhv28eGW nE485B182vpSZEM22diMY4EIWcAupMzMeLhVUkH4PHfxzR5ITX+B5kFoLjXRaKN+Ioei aJcLxAKUu7n1eaMI1qDgWpKXq8Fo+r03kSKS8OI9hCnHVJjMmvZfXZEc6YdUrLEM36wF 4v91Dluek6McyCc+/1WPEmCAB8BFvrB6PHGVrDX5YgDc8lXQNhKtBV8lVzQ4z3z5W6Dy KbPw== X-Received: by 10.14.194.195 with SMTP id m43mr51236493een.44.1360596731886; Mon, 11 Feb 2013 07:32:11 -0800 (PST) MIME-Version: 1.0 Sender: bmathus@gmail.com Received: by 10.14.136.15 with HTTP; Mon, 11 Feb 2013 07:31:50 -0800 (PST) In-Reply-To: <5118FFDD.1030007@artifact-software.com> References: <5118B740.6010908@mgm-tp.com> <5118FFDD.1030007@artifact-software.com> From: Baptiste MATHUS Date: Mon, 11 Feb 2013 16:31:50 +0100 X-Google-Sender-Auth: Gq9UK5rSdcbPoTtPEhr4QBtsGgE Message-ID: Subject: Re: Dependency resolution kicks in too early To: Maven Users List , rwheeler@artifact-software.com Content-Type: multipart/alternative; boundary=047d7b342c4ce2fddf04d5749c61 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b342c4ce2fddf04d5749c61 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable +1. The right approach is to use a MRM. You were unlucky to find an article that is actually more a quite dirty hack than a solution. You shouldn't put dependencies inside your SCM. Put those dependencies once into the maven repository manager, and be happy with a clean and simple build. Cheers 2013/2/11 Ron Wheeler > Why not just load these stray orphans into your MRM once and then treat > them and normal dependencies. > > Ron > > > On 11/02/2013 4:17 AM, Reinhard N=C3=A4gele wrote: > >> Hello, >> >> A couple of years ago I used a plugin execution in the validate phase to >> bootstrap jars that were not available on Maven Central as suggested in >> [1]. I needed to do the same thing again today but noticed that this >> approach does not seem to work any more with Maven 3. Right after runnin= g >> Maven, dependency resolution kicks in making the build fail even before = the >> install plugin gets a chance to install the missing dependency. Here's w= hat >> I'm doing: >> >> >> org.apache.maven.**plugins >> maven-install-**plugin >> >> >> boostrap-some-depencency >> >> install-file >> >> validate >> >> com.some.groupid >> some-artifact >> ${some.artifact.**version} >> jar >> bootstrap-lib/some-**artifact-${some.artifact.**version}.jar >> bootstrap-lib/some-**artifact-${some.artifact.**version}-source= s.jar >> >> >> >> >> >> ... >> >> com.some.groupid >> some-artifact >> ${some.artifact.**version} >> >> ... >> >> 1.2.3 >> >> >> [1] http://www.blackbit.be/2010/**04/15/maven-automatically-** >> install-dependencies-during-**build/ >> >> Is this no longer possible? I'd really prefer this approach over using a >> system dependency. >> >> Thanks, >> Reinhard >> >> >> ------------------------------**------------------------------**--------= - >> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org >> For additional commands, e-mail: users-help@maven.apache.org >> >> >> > > -- > Ron Wheeler > President > Artifact Software Inc > email: rwheeler@artifact-software.com > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org > For additional commands, e-mail: users-help@maven.apache.org > > -- > Baptiste MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! nbsp;! > --047d7b342c4ce2fddf04d5749c61--