Return-Path: Delivered-To: apmail-maven-dev-archive@www.apache.org Received: (qmail 144 invoked from network); 16 Jun 2010 08:27:32 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 16 Jun 2010 08:27:32 -0000 Received: (qmail 55075 invoked by uid 500); 16 Jun 2010 08:27:31 -0000 Delivered-To: apmail-maven-dev-archive@maven.apache.org Received: (qmail 54478 invoked by uid 500); 16 Jun 2010 08:27:29 -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 54463 invoked by uid 99); 16 Jun 2010 08:27:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jun 2010 08:27:27 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of odeaching@gmail.com designates 209.85.212.43 as permitted sender) Received: from [209.85.212.43] (HELO mail-vw0-f43.google.com) (209.85.212.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jun 2010 08:27:19 +0000 Received: by vws11 with SMTP id 11so1289249vws.30 for ; Wed, 16 Jun 2010 01:26:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=lqwsXX3p3xG0Nj+owHIuW9k6lDz+V+Z7VI18lSTrnTo=; b=Fhbu1Wqxqb0Te0Sa/mGuSHkhbIv3iGCYcivbC9Y5cdldApPKTBMR5DHBWNf1C2uDQ+ Jn+AAr2OvSuRuuYo/i8SF/0pxBEkXyqID1KRddL919lSOGfMF7ETMystQwDEPEFbcMkD W2Uk0nuZQAHaNq5sYmP9ET/obcsffsKg7FGgg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=A2sTeSMS0laF8k/17RUeQ903kcDd5QDY6WUHLZmldSTzNGeGaOVGLH62xptus3ic1a 9XRvSF7xoMZajJ/cfCR4Spx7fM2Goa+vupo0BVufuxjYwjQKfaPQD5CMRRhzAxwzHBHK EzIQGP5KbWehTGn3DQNSHOH7AH20L+fq2ZtrI= MIME-Version: 1.0 Received: by 10.229.221.134 with SMTP id ic6mr3565554qcb.65.1276676815434; Wed, 16 Jun 2010 01:26:55 -0700 (PDT) Sender: odeaching@gmail.com Received: by 10.229.239.147 with HTTP; Wed, 16 Jun 2010 01:26:55 -0700 (PDT) Date: Wed, 16 Jun 2010 16:26:55 +0800 X-Google-Sender-Auth: lCdtE-C0Iim4tQh-eVQ-4TWs81k Message-ID: Subject: Runing TCK tests in Maven SCM From: Deng Ching To: Maven Developers List Content-Type: multipart/alternative; boundary=00163630fed713b48c0489217ccb X-Virus-Checked: Checked by ClamAV on apache.org --00163630fed713b48c0489217ccb Content-Type: text/plain; charset=ISO-8859-1 Hi All, I'm currently working on SCM-558 (Add support for 'mkdir' command) and I was wondering how to run the TCK tests in Maven SCM? When I built the project with clean install, there weren't any SCM provider TCK tests executed. I also checked maven-scm-test and saw that there are a couple of TCK tests for the different SCM commands in src/main/java but how do I run them? Thanks in advance! -Deng --00163630fed713b48c0489217ccb--