Yes, for example we have a shell script that runs every so often from a cron job to make everything in our releases repository read-only. We have a separate repository for internal snapshots, so developers can snapshot away.
I've also used the Archiva users to restrict access to deploying to the releases repository so that developers cannot deploy there -- only the build server can so we know which JVM version, environment etc was used and that the build passed (unit tests pass etc). Ben > -----Original Message----- > From: Wendy Smoak [mailto:[EMAIL PROTECTED] > Sent: 02 December 2008 20:18 > To: [email protected] > Subject: Re: Forbid the deploy of the same version > > > I am wondering if there is any way in Archiva, to stop a regular user > > (guest) or other to deploy the same version twice??? > > > > Example: If I just deployed version 1.0.0, then can I stop another > user > > from deploying the same version???? > > For the moment I think the only way would be to change the permissions > at the file system level so the files can't be overwritten. > > However, the option has been requested in both the Deploy plugin [1] > and Archiva [2]. > > [1] http://jira.codehaus.org/browse/MDEPLOY-74 > [2] http://jira.codehaus.org/browse/MRM-747 > > -- > Wendy This e-mail is confidential and intended solely for the use of the individual(s) to whom it is addressed. Any views or opinions expressed are those of the author. If you are not the intended recipient, please be advised that any use, dissemination, printing or copying of this email is strictly prohibited.
