Return-Path: Delivered-To: apmail-maven-continuum-dev-archive@www.apache.org Received: (qmail 74880 invoked from network); 11 Jul 2006 11:10:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 11 Jul 2006 11:10:19 -0000 Received: (qmail 13351 invoked by uid 500); 11 Jul 2006 11:10:18 -0000 Delivered-To: apmail-maven-continuum-dev-archive@maven.apache.org Received: (qmail 13332 invoked by uid 500); 11 Jul 2006 11:10:18 -0000 Mailing-List: contact continuum-dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-dev@maven.apache.org Delivered-To: mailing list continuum-dev@maven.apache.org Received: (qmail 13321 invoked by uid 99); 11 Jul 2006 11:10:18 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jul 2006 04:10:18 -0700 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 (asf.osuosl.org: domain of lists@nabble.com designates 72.21.53.35 as permitted sender) Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jul 2006 04:10:17 -0700 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1G0G7p-0006jY-Gu for continuum-dev@maven.apache.org; Tue, 11 Jul 2006 04:09:57 -0700 Message-ID: <5267279.post@talk.nabble.com> Date: Tue, 11 Jul 2006 03:57:47 -0700 (PDT) From: Ahmed Omarjee To: continuum-dev@maven.apache.org Subject: Listeners for build events MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-Sender: ahmed.omarjee@standardbank.co.za X-Nabble-From: Ahmed Omarjee X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi, I have a requirement to perform other operations before checkout of a project, as well as after a successful or failed build. The context of why I need this is as follows; I am using PVCS at a corporate client, and have already begun writing a maven-scm-plugin for PVCS (I can't sit around waiting for Serena to contribute their plugin). Using agile methodology, I would normally perform a checkout, start the build process (if changes are detected), and on successful build apply a label to the source repository. But alas, PVCS does not have metadata locally thus a label can not be applied to the version that was originally checked out, which may result in inconsistencies. A solution we have come it with (read hack), is : - label the repository before checkout with a tag (eg. Building #123 - 01/07/2006 9:00) - checkout using that label - perform the build - and on success rename the label (which strangely PVCS supports) (eg. Build #123 - 01/07/2006 9:00) - and on failure the label is removed (which strangely PVCS also supports) If only we could have listeners to some important events such as build start, on success, on failure, build finished, etc. this could be pluggable behaviour. I don't mind having a look at this and take up the challenge of maybe implementing it, but I need some guidance and advice on the appropriateness of this as a solution. Ahmed -- View this message in context: http://www.nabble.com/Listeners-for-build-events-tf1923745.html#a5267279 Sent from the Continuum - Dev forum at Nabble.com.