Return-Path: Delivered-To: apmail-continuum-users-archive@www.apache.org Received: (qmail 27806 invoked from network); 23 Dec 2008 00:33:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Dec 2008 00:33:43 -0000 Received: (qmail 34888 invoked by uid 500); 23 Dec 2008 00:33:42 -0000 Delivered-To: apmail-continuum-users-archive@continuum.apache.org Received: (qmail 34851 invoked by uid 500); 23 Dec 2008 00:33:42 -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 34840 invoked by uid 99); 23 Dec 2008 00:33:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Dec 2008 16:33:42 -0800 X-ASF-Spam-Status: No, hits=-1.8 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of batkinson@usm.maine.edu designates 130.111.135.148 as permitted sender) Received: from [130.111.135.148] (HELO mail0.doit.usm.maine.edu) (130.111.135.148) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Dec 2008 00:33:33 +0000 Received: from uct5.uct.usm.maine.edu (uct5.doit.usm.maine.edu [130.111.135.97]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail0.doit.usm.maine.edu (Postfix) with ESMTP id C3815BA082 for ; Mon, 22 Dec 2008 19:33:08 -0500 (EST) Received: from UCT5-MTA by uct5.uct.usm.maine.edu with Novell_GroupWise; Mon, 22 Dec 2008 19:33:08 -0500 Message-Id: <494FEB5A0200009D000202D4@uct5.uct.usm.maine.edu> X-Mailer: Novell GroupWise Internet Agent 8.0.0 Date: Mon, 22 Dec 2008 19:32:42 -0500 From: "Brent Atkinson" To: Subject: Re: Installations and Build Environments References: <494A86230200009D0001FFE2@uct5.uct.usm.maine.edu> <494B69F30200009D00020065@uct5.uct.usm.maine.edu> In-Reply-To: <494B69F30200009D00020065@uct5.uct.usm.maine.edu> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=__PartFAD2EEBA.0__=" X-USM-MailScanner-Watermark: 1230597191.58994@D7CFFItN9NaJoW/3+VVtVw X-Virus-Checked: Checked by ClamAV on apache.org --=__PartFAD2EEBA.0__= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I created an issue in JIRA under Continuum-Documentation. I wasn't sure = what to do about the binary files so I attached the svn diff and a zip of the = changed=20 (and added) images: http://jira.codehaus.org/browse/CONTINUUM-2025. =20 How should one normally handle binary files in a patch? =20 Thanks, =20 Brent >>> "Wendy Smoak" 12/18/2008 5:48 PM >>> On Thu, Dec 18, 2008 at 3:19 PM, Brent Atkinson = wrote: > Build Definitions allow you to set which Build Environment they use. Is = the intent > that you should use these to have multiple simultaneous Java, Maven and = Ant > installations and setting the Build Environment for the Build Definition = sets the > corresponding environment variables when the shell commands are run? Yes. For example, you may have one project that has to build with Maven 2.0.5 and JDK 1.4, while another needs Maven 2.0.9 and JDK 1.6. The default will be the environment for the user Continuum is running as, which may not be correct for all projects. Patches or suggestions for the docs are welcome if you'd like to help improve them after you work with these features for a bit. --=20 Wendy --=__PartFAD2EEBA.0__=--