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