Use a cron job to change file permission and owners of the repostioty
content.
Cheers,
Siegfried Goeschl
On 30.06.10 07:38, Jemos Infra wrote:
No, we don't use Nexus, just the file system. We've got a single account
(sys_account) who is entitled to upload to this repository through ssh
using an infrastructure given key, so also the possibility to use
multiple usernames/passwords doesn't seem feasable. Any other
suggestions?
Regards,
M.
On Tue, 2010-06-29 at 16:22 -0700, Manfred Moser wrote:
Hi all,
I've got the requirement of providing different settings.xml files to
different "clients". Currently we've got different repositories: Third
Party (TP), SNAPSHOTS and Releases. Each "client" has got different
requirements. For instance, developers can only use all repositories as
read-only, our CI environment can upload artifacts to the SNAPSHOT but
have read-only access to TP and Releases while our build software can
only upload to Releases but have read-only to TP and SNAPSHOTS.
Is there a way to setup this kind of configuration via settings.xml or
other elements inside a POM? So far it seems I couldn't find a way.
Just use different username/password combinations in your repository
server with different access rights and use the different roles in pom.xml
profiles and settings.xml.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
