Return-Path: Delivered-To: apmail-maven-dev-archive@www.apache.org Received: (qmail 56523 invoked from network); 3 Dec 2007 15:14:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Dec 2007 15:14:12 -0000 Received: (qmail 12185 invoked by uid 500); 3 Dec 2007 15:13:58 -0000 Delivered-To: apmail-maven-dev-archive@maven.apache.org Received: (qmail 12122 invoked by uid 500); 3 Dec 2007 15:13:58 -0000 Mailing-List: contact dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Developers List" Reply-To: "Maven Developers List" Delivered-To: mailing list dev@maven.apache.org Received: (qmail 12111 invoked by uid 99); 3 Dec 2007 15:13:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Dec 2007 07:13:58 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [64.79.197.59] (HELO mesa2.com) (64.79.197.59) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Dec 2007 15:13:35 +0000 Received: from [24.147.10.180] (account jdkulp HELO [192.168.1.101]) by mesa2.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 1543167 for dev@maven.apache.org; Mon, 03 Dec 2007 10:13:32 -0500 From: Daniel Kulp To: dev@maven.apache.org Subject: Please check/fix permissions in m2-ibiblio-rsync-repository after deploy Date: Mon, 3 Dec 2007 10:13:30 -0500 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200712031013.31037.dkulp@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org I just ran into an issue with the maven-metadata.xml file being non group writable causing the stage plugin to "hang" (in actuality, it was waiting for the overwrite y/n prompt). stage probably could use the "-f" option on mv to force it, but..... (actually, stage COULD also do a "chmod g+w" to fix things) In anycase, could everyone that has done a release lately please check the permisions. Especially on the maven-metadata.xml files as that can block anyone else from doing releases in the future. In anycase, doing something like: cd /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/maven chmod -R g+w * would fix any issues. The important ones: maven-shade-plugin/maven-metadata.xml: maven-javadoc-plugin/maven-metadata.xml: maven-invoker-plugin/maven-metadata.xml: maven-clean-plugin/maven-metadata.xml: maven-assembly-plugin/maven-metadata.xml: maven-patch-plugin/maven-metadata.xml: maven-war-plugin/maven-metadata.xml: maven-site-plugin/maven-metadata.xml: Thanks! -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 daniel.kulp@iona.com http://www.dankulp.com/blog --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org