since the problem is with maven-metadata.xml* files, not parent directory, there is a Unix trick to fix the permissions without waiting for the owner to do it: copy the files to new ones and remove old ones
for f in maven-metadata.xml*; do mv $f $f~; cp $f~ $f; chmod g+w $f; rm -f $f~; done I just did it on pmd plugin 2.4-SNAPSHOT: you can deploy the snapshot now Hervé Le samedi 19 avril 2008, Brian E. Fox a écrit : > You'll have to check who owns them and ask them to run the > fix-permissions script in the root of the m2-snap repo. > > -----Original Message----- > From: Benjamin Bentmann [mailto:[EMAIL PROTECTED] > Sent: Friday, April 18, 2008 7:09 PM > To: Maven Developers List > Subject: Deployment of maven-pmd-plugin:2.4-SNAPSHOT > > Hi, > > I wanted to deploy a new 2.4-snapshot of the PMD Plugin but failed > because > the existing metadata files are not group-writable. Can somebody help > and > fix the file permissions? > > > Benjamin > > > --------------------------------------------------------------------- > 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]
