Mailing-List: contact users-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@continuum.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Non-Recursive Build Question
Date: Wed, 9 Apr 2008 17:48:38 -0500
Message-ID: 
 <69AB3F80173BDD46960FB60E86DF94F8058DF71E@MKEXCHVS2.Mail.Fiserv.net>
Thread-Topic: Non-Recursive Build Question
Thread-Index: Aciak9n1z6pdPdSHQeG6YBxFsnuz5A==
From: "Harper, Brad" <brad.harper@epsiia.com>
To: <users@continuum.apache.org>

Hello:

I have a multi-module maven project. As its build, I'd like to install
it before proceeding with the builds for a small subset of its
sub-projects. The 'install' is intended so that correct
<dependencyManagement> is defined for its modules.

I've created a Continuum project group, a member of which is this
top-level project. It's build defined as '--non-recursive
install:install', but when the build is initiated, *all* of the contents
at the scm url are checked out into the working directory. All I need to
build and install this project is the project's pom.xml itself.

How do I suppress the checkout to match the --non-recursive nature of
the build?

Thanks.

Brad Harper