From users-return-130889-apmail-maven-users-archive=maven.apache.org@maven.apache.org Wed Jan 23 14:32:18 2013 Return-Path: X-Original-To: apmail-maven-users-archive@www.apache.org Delivered-To: apmail-maven-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0A091E6E4 for ; Wed, 23 Jan 2013 14:32:18 +0000 (UTC) Received: (qmail 15146 invoked by uid 500); 23 Jan 2013 14:32:16 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 14944 invoked by uid 500); 23 Jan 2013 14:32:15 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 14926 invoked by uid 99); 23 Jan 2013 14:32:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Jan 2013 14:32:15 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jieryn@gmail.com designates 209.85.219.46 as permitted sender) Received: from [209.85.219.46] (HELO mail-oa0-f46.google.com) (209.85.219.46) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Jan 2013 14:32:08 +0000 Received: by mail-oa0-f46.google.com with SMTP id h16so8487782oag.19 for ; Wed, 23 Jan 2013 06:31:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=75OlTEIYHPBLROqpB049h++9I8Kmp1C25q+NoXGmbnw=; b=jAjdF4F5cslilZQKnED9TqprZWd2Ke9PTwcULsxkN0UrE+JUKgW20nO2cZXBvX3sQy loPpofN/htyZW1mf3iVNx7U6Uo8DKWn44G7X6sAiqWr8bVVcQQxkenBzIYa9Va+jZ1gX KUI8uwgXPMuCBZnilDTOWufnxFjxSE9ucMHRzPRpN7GMTamKILzmAV5UNfUuERyi/tca Ypkx51Qs829eYKgMOXJddKKOVC9yYgP50CaqeNq9WJ2txheaSiV03YYmErt7XYZ4mhAk fI19O6nl/8NVgkGzXpFx56rFaTlhlf7bW9+K0KFDPg3CJ29BibIHlCl+BMopFX4r68WA kiaw== MIME-Version: 1.0 X-Received: by 10.60.168.236 with SMTP id zz12mr1185834oeb.12.1358951507408; Wed, 23 Jan 2013 06:31:47 -0800 (PST) Received: by 10.182.5.194 with HTTP; Wed, 23 Jan 2013 06:31:47 -0800 (PST) Date: Wed, 23 Jan 2013 09:31:47 -0500 Message-ID: Subject: custom extension problem, error mode enablement From: Jesse Farinacci To: Maven Users List Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Greetings I'm seeing some odd behavior with a custom Apache Maven extension intended to force on error message mode (-e). The extension can be found here https://gist.github.com/63e65486e60124a3e8f7 The extension loads fine, and I see the log message found in the extension, but it doesn't actually enable error message mode! I verify error message mode is not enabled via the extension by causing an error in a project, e.g. dependency on junit:junit:666, and observing the difference with and without -e passed to mvn. Would someone please tell me the magic incantation to programmatically get error message mode enabled? It appears that setting MavenExecutionRequest.setShowErrors(true) should do the trick, but perhaps this is read once and never again, which occurs before the extension gets loaded? Any help is appreciated, -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org