Return-Path: Delivered-To: apmail-archiva-dev-archive@www.apache.org Received: (qmail 47270 invoked from network); 1 Mar 2010 11:15:02 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Mar 2010 11:15:02 -0000 Received: (qmail 39483 invoked by uid 500); 1 Mar 2010 11:15:01 -0000 Delivered-To: apmail-archiva-dev-archive@archiva.apache.org Received: (qmail 39447 invoked by uid 500); 1 Mar 2010 11:15:01 -0000 Mailing-List: contact dev-help@archiva.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@archiva.apache.org Delivered-To: mailing list dev@archiva.apache.org Received: (qmail 39439 invoked by uid 99); 1 Mar 2010 11:15:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Mar 2010 11:15:01 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Mar 2010 11:14:52 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Nm3a4-00086R-41 for dev@archiva.apache.org; Mon, 01 Mar 2010 03:14:32 -0800 Message-ID: <27742269.post@talk.nabble.com> Date: Mon, 1 Mar 2010 03:14:32 -0800 (PST) From: Marc Lustig To: dev@archiva.apache.org Subject: MRM-1351: please advise MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ml@marclustig.com X-Virus-Checked: Checked by ClamAV on apache.org Hi there, I have just created MRM-1351 and have a couple of questions: 1) supported protocols Maven Deploy Plugin supports next to DAV also FTP- and SSH-based artifact deployment. Which of those additional protocols does Archiva support? Accordingly, which is the proper place for a generic implementation of the hashcode-based artifact validation? 2) getting the hashcode of the local repo The maven-deploy-plugin does not support to specify a parameter like "sha-hashcode", neither for the deploy nor the deploy-file subgoal. How then could Archiva possibly get the hashcode of the local repo from? This appears to me a major pre-condition to implement this ticket. cheers Marc -- View this message in context: http://old.nabble.com/MRM-1351%3A-please-advise-tp27742269p27742269.html Sent from the archiva-dev mailing list archive at Nabble.com.