Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-users@maven.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C63946.069DAFF4"
Subject: Problem with remote repos
Date: Fri, 24 Feb 2006 08:27:24 -0500
Message-ID: <2BABBE7D2A66E04DB8A66A527D29927E0BDF03@intrepid.infinity.nu>
Thread-Topic: Problem with remote repos
Thread-Index: AcY5Rgwcz/37UynKTSe8kKUuKLEuZg==
From: "Brian E. Fox" <brianf@reply.infinity.nu>
To: <continuum-users@maven.apache.org>

------_=_NextPart_001_01C63946.069DAFF4
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Is there a known problem with 1.0.2 and using remote repositories? I
have my settings.xml in the correct place because it is finding
artifacts from the local repo but not the remote one. Here's what's
happening:
=20
I have a build running every hour. I have a common parent from which
this derives. I update and deploy this parent from a computer different
than continuum. I check in the code. Continuum goes to build and fails
because it can't find the parent. If I repeat this except before
continuum runs, I checkout the parent and install on the continuum
machine, it works fine. The settings file is an exact copy of the one
maven is using and all builds work perfectly with maven.=20
=20
So it seems like continuum somehow isn't reading or using the remote
repositories.

------_=_NextPart_001_01C63946.069DAFF4--