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 anders.g.hammar@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:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=tcnBeKcm1ahT6KFl1RiC2+hNOxSGkVDIfU56u+u4mM5+uk+oRpt/5Hv0Oz54KTUJIi
         mve91VWDQPSDdfuzJ6SokGyBtD4sdd4JbjcJtYYtrKbWGKX21zO5Czt1iPBwyLTirGUO
         gnjU9cKMKbZTaPMQnPiEQCv8q2IUh0/lOHUXs=
MIME-Version: 1.0
Sender: anders.g.hammar@gmail.com
In-Reply-To: <AANLkTin=mbWH+-hvaoOAt4w7uwg=8xB+9vHnT4fTuwYj@mail.gmail.com>
References: <AANLkTi=UqoWgLF0H8sATqq2LHy1Yiz2L-aO+A-Lj5KfA@mail.gmail.com>
	<AANLkTin=mbWH+-hvaoOAt4w7uwg=8xB+9vHnT4fTuwYj@mail.gmail.com>
Date: Mon, 4 Oct 2010 12:29:19 +0200
Message-ID: <AANLkTikHkxdsorLfu43a1VHK41mAL8q1RdqSfCJvsf4f@mail.gmail.com>
Subject: Re: Company-wide settings
From: Anders Hammar <anders@hammar.net>
To: Maven Users List <users@maven.apache.org>
Content-Type: multipart/alternative; boundary=0015174be98c5e704b0491c8048d

--0015174be98c5e704b0491c8048d
Content-Type: text/plain; charset=ISO-8859-1

One issue with this approach is that m2eclipse will not use this
settings.xml file (by default, as it has it's own embedded Maven). I guess
this could be solved by configuring the standalone Maven installation in
m2eclipse.

Anyone that has actually tried the approach of having a "corporate"
settings.xml bundled with a custom Maven distro?

/Anders

On Mon, Oct 4, 2010 at 11:46, Wendy Smoak <wsmoak@gmail.com> wrote:

> On Sun, Oct 3, 2010 at 5:34 PM, Phillip Hellewell <sshock@gmail.com>
> wrote:
> > The idea is to have a shared "company-level" settings.xml with
> > settings like profiles that most developers will want, and to have
> > them automatically available.  The alternative is for everyone to
> > manually append it to their global or user-level settings.xml.
>
> One way is to make a custom Maven distribution for your organization,
> with a modified settings.xml.
>
> This also has the advantage of having all developers use the same
> version, which makes support easier.
>
> Many organizations don't allow developers to download and install
> random stuff off the internet anyway, so this becomes your
> corporate/approved/official Maven distro.
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

--0015174be98c5e704b0491c8048d--