> > 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.
This is what we do for the most part. We checkout the global settings.xml file to the conf folder of the maven install. This way, if settings ever change, all a dev needs to do is an svn update on the file. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
