With scp deployement some file permissions are setted. (look at filepermissions in your settings). Have look on the deployed artifacts. On a solaris machine : ls -l says : rwxr-xr-x 1 olamy (olamy is my user) I think it's enough protected ;-).
For a snapshot repo filepermissions must be different (because other users can override maven metadata). Note : there is an issue concerning this http://jira.codehaus.org/browse/WAGONSSH-44 A workaround for this is to running a script which correctly set file permissions when you deploy something new (groupId, artifactId or version ): On my corporate env we do (users add this in their crontab) : find /local/maven/maven2/snapshots ! -perm 775 -type d -user $1 -exec chmod 775 {} \; find /local/maven/maven2/snapshots ! -perm 664 -iname maven-metadata.xml* -user $1 -exec chmod 664 {} \; /local/maven/maven2/snapshots is the snapshots repository where are deployed the snapshots artifacts. HTH, - Olivier -----Message d'origine----- De : Plygawko Dariusz (Centrala PZUSA) [mailto:[EMAIL PROTECTED] Envoyé : mardi 23 mai 2006 14:48 À : Maven Users List Objet : RE: How to prevent from deploying the same version of artefact twice? Yes, developing should be done using SNAPHOTs. But still from time to time someone will have to deploy "stable" version (without "-SNAPSHOT") and I after it would like to make this file completly safe and "read-only"(automatically). But I don't know how to... -----Original Message----- From: ben short [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 23, 2006 12:48 PM To: Maven Users List Subject: Re: How to prevent from deploying the same version of artefact twice? Kind of going against the whole idea of maven then. On 5/23/06, Plygawko Dariusz (Centrala PZUSA) <[EMAIL PROTECTED]> wrote: > Is it possible to workaround this problem if I don't want to use > snapshots? :) > > > -----Original Message----- > From: Wim Deblauwe [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 23, 2006 12:14 PM > To: Maven Users List > Subject: Re: How to prevent from deploying the same version of > artefact twice? > > > Use the release plugin, this will automatically change the version to > the next SNAPSHOT version. > > 2006/5/23, dariusz.p <[EMAIL PROTECTED]>: > > > > > > It's possible to overwrite the same version of an artefact (when you > > forget to increment version in pom.xml after you changed something > > in source code). > > How to prevent from it? I use ftp server as internal repository (I can > > switch to sth else if it's necessary). I would prefer to fix it on the > > server side instead of pachting deploy-plugin (there is always a chance > > that > > someone will have a wrong version of it). We have a big team of developers > > and I'm affraid we might have some problems with maven (uncontrolled > > overwriting). > > > > Thank You a lot in advance, > > Dariusz > > -- > > View this message in context: > > http://www.nabble.com/How+to+prevent+from+deploying+the+same+version > > +of+artefact+twice--t1668061.html#a4520449 > > Sent from the Maven - Users forum at Nabble.com. > > > > > > -------------------------------------------------------------------- > > - > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, any attachments and the information contained therein ("this message") are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. -------------------------------------------------------------------------------------------------------------- Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après "le message" ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. ------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
