Return-Path: Delivered-To: apmail-continuum-users-archive@www.apache.org Received: (qmail 71901 invoked from network); 28 Jul 2008 23:44:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Jul 2008 23:44:19 -0000 Received: (qmail 85952 invoked by uid 500); 28 Jul 2008 23:44:17 -0000 Delivered-To: apmail-continuum-users-archive@continuum.apache.org Received: (qmail 85926 invoked by uid 500); 28 Jul 2008 23:44:17 -0000 Mailing-List: contact users-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@continuum.apache.org Delivered-To: mailing list users@continuum.apache.org Received: (qmail 85915 invoked by uid 500); 28 Jul 2008 23:44:17 -0000 Delivered-To: apmail-maven-continuum-users@maven.apache.org Received: (qmail 85912 invoked by uid 99); 28 Jul 2008 23:44:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jul 2008 16:44:17 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of apache.maillist@gmail.com designates 209.85.132.251 as permitted sender) Received: from [209.85.132.251] (HELO an-out-0708.google.com) (209.85.132.251) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jul 2008 23:43:23 +0000 Received: by an-out-0708.google.com with SMTP id d40so1050050and.79 for ; Mon, 28 Jul 2008 16:43:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=QByITUOsDTgooAHz3cXttmh4OwjQor7t1aeEMay2O6c=; b=vgwuew+mVCHDbem2YaBa937BSNiqDd6tf3Elyd4EQMANwBGwxoXBKVy2d7eaoTEGDt SZT+IogmPEKtb3AvIp2HuDaxnxJm9WEWbYVCOPG6J2HPBMBe1hsfFRqnL5jyMC73kOv6 loWmUVBHf2QqK+19ICrOaNc1cTf3/vFnsWLRM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=TzGNAZi+Ze8/bKXdhMV57CYEFA78AKjTZIix2p1HMb2qdn+r+yEuFCEM9H2PebZqyK A26LUme4hYsPO9xNPGqlqRon+zvvzmSICEYUdiHaiQU6PtKPdnaMHPRmq5ArlPU1R99f aHEQwul3yFtyWiqeqG7WuRa2GlxgDoxwu5sDQ= Received: by 10.100.139.20 with SMTP id m20mr9283748and.135.1217288628312; Mon, 28 Jul 2008 16:43:48 -0700 (PDT) Received: by 10.101.69.13 with HTTP; Mon, 28 Jul 2008 16:43:48 -0700 (PDT) Message-ID: <61ebb7260807281643s64f90518ka659a6d11a125aff@mail.gmail.com> Date: Mon, 28 Jul 2008 16:43:48 -0700 From: "L. J." To: continuum-users Subject: question about comments from Emmanuel on Continuum 1.1 dependency management MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_58431_26970022.1217288628295" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_58431_26970022.1217288628295 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I have a question about comments from Emmanuel below: Projects B depends on Project A. If project A have some changes, it is built, then even if project B doesn't have changes, it will be built too because it depends on project A that have changed. So where/how does Continuum check the dependency changes in order to build Project B? Does it check Project A's changes in source control (such as CVS, SVN), or it checks/compare the local Maven repo on the timestamp that the last time Project A and Project B were built/installed? Thanks. LJ ------=_Part_58431_26970022.1217288628295--