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 (nike.apache.org: domain of gjeudy@teksystems.com
 designates 216.152.100.65 as permitted sender)
Content-Transfer-Encoding: 7bit
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Importance: normal
Priority: normal
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C9861A.4658C70F"
Subject: Re-use global distributionManagement
Date: Tue, 3 Feb 2009 11:12:56 -0500
Message-ID: 
 <8CAF6A21E6DE484DABFBCF990223F650100E62@ag00-exmbx06.allegisgroup.com>
Thread-Topic: Re-use global distributionManagement
thread-index: AcmGGkZYschEyj6uRRG/6YMwVzoylQ==
From: "Jeudy, Guillaume" <gjeudy@teksystems.com>
To: <users@maven.apache.org>

------_=_NextPart_001_01C9861A.4658C70F
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi maven users,
=20
I have distributionManagement information that is common to all projects =
at my company. Do you know of any tricks to ensure all projects share =
the same distributionManagement info? I don't want to use pom hierarchy =
if possible because that would mean I would need a master top-level pom =
that sits somewhere in SVN that everyone need to checkout for it to be =
resolved.
=20
Ideally I would like to inherit pom distributionManagement from a =
dependency that lives in the repo. Is it possible to do this? This way =
no matter from where you are building a proj you can inherit firmwide =
pom settings as long as the pom artifact is stored in the company repo.
=20
Thanks,
-Guillaume


_________________________________________________________________________=
___________________________
This electronic mail (including any attachments) may contain information =
that is privileged, confidential, and/or otherwise protected from =
disclosure to anyone other than its intended recipient(s). Any =
dissemination or use of this electronic email or its contents (including =
any attachments) by persons other than the intended recipient(s) is =
strictly prohibited. If you have received this message in error, please =
notify us immediately by reply email so that we may correct our internal =
records. Please then delete the original message (including any =
attachments) in its entirety. Thank you.

------_=_NextPart_001_01C9861A.4658C70F--