Not ideal, but you could set up a cron job or similar to frequently set -w to all the files in your deploy directories. Then you couldn't overwrite things due to filesystem privileges.
Wayne On 9/26/07, Hayes, Peter <[EMAIL PROTECTED]> wrote: > Yes that is true. We are using clearcase though and the release plugin > has some limitations with regards to clearcase. > > I thought though that once a release is made, it should never be changed > as it is in the "wild" and may have already been used. For instance, I > think recently the maven developers had a problem with the release of > the archetype plugin and they did not just re-release that version, they > moved to a new one. If this is the recommended process, then I would > think it would be appropriate for the deploy command to (at least by > default) not allow the overwriting of an existing artifact. > > Pete > > -----Original Message----- > From: John Coleman [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 26, 2007 10:46 AM > To: Maven Users List > Subject: RE: Deploying same version overwrites existing release > > But if you use relase:prepare/release:perform then your snapshot version > number goes up afterwards and overwritting is impossible? > > John > > -----Original Message----- > From: Hayes, Peter [mailto:[EMAIL PROTECTED] > Sent: 26 September 2007 15:39 > To: Maven Users List > Subject: Deploying same version overwrites existing release > > Is there a way to configure maven to not allow it to deploy over an > existing release artifact? > > Peter Hayes > Architecture & Shared Technology Services | Fidelity Investments > Management Technology > > > Eurobase International Limited and its subsidiaries (Eurobase) are > unable to exercise control over the content of information in E-Mails. > Any views and opinions expressed may be personal to the sender and are > not necessarily those of Eurobase. Eurobase will not enter into any > contractual obligations in respect of any part of its business in any > E-mail. > > Privileged / confidential information may be contained in this message > and /or any attachments. This E-mail is intended for the use of the > addressee(s) only and may contain confidential information. If you are > not the / an intended recipient, you are hereby notified that any use or > dissemination of this communication is strictly prohibited. If you > receive this transmission in error, please notify us immediately, and > then delete this E-mail. > > Neither the sender nor Eurobase accepts any liability whatsoever for any > defects of any kind either in or arising from this E-mail transmission. > E-Mail transmission cannot be guaranteed to be secure or error-free, as > messages can be intercepted, lost, corrupted, destroyed, contain > viruses, or arrive late or incomplete. Eurobase does not accept any > responsibility for viruses and it is your responsibility to scan any > attachments. > > Eurobase Systems Limited is the main trading company in the Eurobase > International Group; registered in England and Wales as company number > 02251162; registered address: Essex House, 2 County Place, Chelmsford, > Essex CM2 0RE, UK. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
