maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yanko, Curtis" <>
Subject RE: Company-wide settings
Date Mon, 04 Oct 2010 12:09:38 GMT
We do. It is simply a requirement for the AppDev team to implement. So,
even when they forget, we catch it in the build process since those
builds happen on our servers where the settings.xml is definitely set to
use our internal repository.


Curt Yanko | Continuous Integration Services
Making IT Happen, one build at a time

-----Original Message-----
From: [] On
Behalf Of Anders Hammar
Sent: Monday, October 04, 2010 6:29 AM
To: Maven Users List
Subject: Re: Company-wide settings

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?


On Mon, Oct 4, 2010 at 11:46, Wendy Smoak <> wrote:

> On Sun, Oct 3, 2010 at 5:34 PM, Phillip Hellewell <>
> 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:
> For additional commands, e-mail:

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message