Maybe this could be a configuration option for a project group.
Allow running builds in a chroot jail
Project group admin should not be able to change the local repository
Add a feature to allow cleaning the m2 local repo once every N days
Linking to CONTINUUM-1879 – the security doesn't seem right here, a project group admin can select a different local repo which may contain artifacts he isn't supposed to have access to.
fixed in rev 681492.
This is also related to CONTINUUM-782. I'm thinking of having the local maven repo associated with the build definition.
This might be addressed by Carlos' work on CONTINUUM-1731