maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ziga GREGORIC <>
Subject Re: System-wide, read-only repository
Date Wed, 13 Nov 2013 17:41:56 GMT
I'd go for what Wayne is suggesting. Installing Maven Repository Manager on
laptops? hmmm... It will cause artifacts to be duplicated in .m2/repository
and in Nexus/Artifactory folder structure.

There's no way (IMHO) of forcing users not to change settings.xml - but if
provided template works for most cases, not many will see the need to
change anything. Having control over repos used or artifacts allowed can be
accomplished on a project level.

My suggestion is to set-up organisation-wide repository, proxy to central,
codehous, jboss, ..., then:
1) Route everything through it with <mirror> configured, together with a)
routes defined (in case of Nexus) and b) take extra care of <mirrorOf> (see - Adv.
Mirror Spec)
2) When setting repositories override <updatePolicy> daily (default) with
never for releases repositories. (I consider re-release of an artifact bad
idea anyway).



On Wed, Nov 13, 2013 at 4:23 PM, Wayne Fay <> wrote:

> > It's the students first contact with Maven (and with tons of other
> > tools), so we really need to make it easy for them (and for the
> > teacher's team too, indeed, we have a bunch of things to maintain, and
> > reducing the list by one is nice). Keeping the default configuration as
> > much as possible is a real gain here (nothing to configure, works at
> > school, works on their laptop too).
> You could also offer your own packaging of Maven with a customized
> settings.xml etc to make things even easier on your students. This is
> typical in sufficiently large corporate environments.
> Wayne
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message