Mailing-List: contact dev-help@yetus.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@yetus.apache.org
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Yetus design question
From: Allen Wittenauer <aw@effectivemachines.com>
In-Reply-To: <81BB1B02-54F8-4C97-959E-784716F58821@cloudera.com>
Date: Wed, 24 May 2017 11:07:20 -0700
Cc: Casey Brotherton <cbrotherton@cloudera.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E5AC6C21-2CD9-4E5B-B589-DDF39F6B6579@effectivemachines.com>
References: <81BB1B02-54F8-4C97-959E-784716F58821@cloudera.com>
To: dev@yetus.apache.org
archived-at: Wed, 24 May 2017 18:07:28 -0000


> On May 24, 2017, at 6:36 AM, Peter Vary <pvary@cloudera.com> wrote:
>=20
> Hi Team,
>=20
> As working on integrating Yetus to Hive, I come around the following =
problem:
>=20
> I run Yetus on a clean machine without compiling the project =
previously.
> This means that the I do not have the original artifacts in my maven =
repository.
> When Yetus test-patch.sh tries to run the compilation on the specific =
modules which are require modules which are not changed then maven will =
not find the arifacts, and not able to compile.
>=20
> I can run a maven clean install on the project, but I am not sure this =
is the best possible solution.
>=20
> Could someone help me how this problem solved in other projects? Do =
they use an initialized repository, or do they compile it themselves?


	Yetus should be running maven install itself very early in a =
test run (generally right after all the pre-checks).  Is 'mvninstall' =
not enabled?  Is mvninstall failing?  When I've seen failures, it is =
usually because there are problems with the dependency DAG that a =
populated repo won't hit...