Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 33044 invoked from network); 6 Apr 2007 15:27:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Apr 2007 15:27:08 -0000 Received: (qmail 76911 invoked by uid 500); 6 Apr 2007 15:27:15 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 76674 invoked by uid 500); 6 Apr 2007 15:27:14 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 76665 invoked by uid 99); 6 Apr 2007 15:27:14 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Apr 2007 08:27:14 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of tim.morrow@gmail.com designates 66.249.92.174 as permitted sender) Received: from [66.249.92.174] (HELO ug-out-1314.google.com) (66.249.92.174) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Apr 2007 08:27:06 -0700 Received: by ug-out-1314.google.com with SMTP id m3so1296480ugc for ; Fri, 06 Apr 2007 08:26:43 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=RKM0WQVbHzD8oevZxPFqXtZaibILletDG7vxmkAiMCH6xBXvqQvQlylD9b95GylXCGLNRx364Of6DtDc72wXYkqdAAR5i0BRfcxT4dmpXJkRqluK8LVrylihSbxZBSsE65XriU+uMCWlgGto5RfbUQ8TRbv/eQ4tbqH/kOKjZA8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ggR8T046445cPCW8WMHZQUviR+nYEakT29VcXQJ/SaDCuXRVhHTLp9t8UFCUMrDwrSZZsP+6ikuzIK4mz/IkeMaoPi56rVvG2q/sKC2w+OjL43rBMaHt1+nNUFB0N9zOeQ8Jf9AFhHAqpbMdZnFX46Ve2ITtT1ry0qlCGwEi4GE= Received: by 10.66.244.10 with SMTP id r10mr3055047ugh.1175873203022; Fri, 06 Apr 2007 08:26:43 -0700 (PDT) Received: by 10.67.9.17 with HTTP; Fri, 6 Apr 2007 08:26:42 -0700 (PDT) Message-ID: <92c218d10704060826j82f1eb2q7e74726ab607c6db@mail.gmail.com> Date: Fri, 6 Apr 2007 08:26:42 -0700 From: "Tim Morrow" To: users@activemq.apache.org Subject: Controlling location of activemq-data with maven plugin MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org Right now when I start the broker via the Maven plugin, it creates the "activemq-data" directory in the directory from which I'm executing Maven (the source directory) . Given that I'm using the plugin for integration-tests, I'd like to place activemq-data in the target directory so that it is deleted automatically when I execute the "clean" target. After digging around, I found in org.apache.activemq.util.IOHelper that there is a system property (org.apache.activemq.default.directory.prefix) that controls the placement of this directory. It seems like it might be sensible for the maven plugin to use the already defined "outputDirectory" configuration setting (which defaults to target). Does this make sense? I don't know if keeping the activemq-data directory around adds value when using the maven plugin. With the above mod, it will remain until you do a "clean". I'll create a patch. Thanks, Tim