Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of hilco.wijbenga@gmail.com
 designates 209.85.215.43 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=w0KsY5c5eI3mjx1Al4QhtC+7WiLszHet84+KURdWdfiaSHnrLPAodl4jhtmFLKfYPb
         k9jOtsLxncvYN7eaFP53I2KxvYlXEfTHYyBbp6K4TjWeNmbjTkAWPK1ZKKN1rhurebFY
         ebQXDVAj0fHh6EVMmrcgGUUV9AcMODx8syplA=
MIME-Version: 1.0
In-Reply-To: <AANLkTincnYyHcK4QUmLNWhL2c+A7f75sS2sQn3YVcuik@mail.gmail.com>
References: <AANLkTikYH0iG=zSkQ7E5EUNv91zNnm5iVqSUNRc5ZWc3@mail.gmail.com>
	<AANLkTinASf_c9e_=yYvuar1dRPS0zj2mrmzK-JEKrd3m@mail.gmail.com>
	<AANLkTinnubPxvwKPgcqoLYfsnHn8YxiM+H3BZyLffi-p@mail.gmail.com>
	<AANLkTincnYyHcK4QUmLNWhL2c+A7f75sS2sQn3YVcuik@mail.gmail.com>
Date: Mon, 4 Oct 2010 13:50:57 -0700
Message-ID: <AANLkTimAq7q7cgWw=z+FqcaV8QSuoNm4f9LUb=aZRPkH@mail.gmail.com>
Subject: Re: Maven 2 & 3 + Hudson + Nexus
From: Hilco Wijbenga <hilco.wijbenga@gmail.com>
To: Maven Users List <users@maven.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 4 October 2010 13:38, Stevo Slavi=C4=87 <sslavic@gmail.com> wrote:
> Check policy settings of any repository definition from where problematic
> (snapshot) dependency is supposed to be fetched from.

The Nexus setup is as follows: Public Repositories (group) contains
Public Snapshot Repositories (group) contains Company Snapshots
(proxy) uses Remote Repository (snapshots).

The proxy has policy snapshots. The group repositories don't seem to
have a policy. This has been working before so I think it's okay.

> Maybe you'll reproduce
> issue locally once you clean your local repository (probably dependency
> artifact is there so you can build locally but hudson can not access
> repository where dependency artifact resides).

Actually I *can* reproduce the issue locally. All I need to do is
remove the problematic POM from my local repository and use Maven 2.
With Maven 3, however, there is no issue.

> Also if you're using
> alternate settings.xml to configure repository access there's a known
> bug<http://issues.hudson-ci.org/browse/HUDSON-4693>in hudson.

I am not using an alternate settings.xml. It's all in
/home/user/.m2/settings.xml.

Cheers,
Hilco

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org