Return-Path: Delivered-To: apmail-struts-user-archive@www.apache.org Received: (qmail 91710 invoked from network); 14 Feb 2006 21:42:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Feb 2006 21:42:52 -0000 Received: (qmail 75468 invoked by uid 500); 14 Feb 2006 21:42:41 -0000 Delivered-To: apmail-struts-user-archive@struts.apache.org Received: (qmail 75441 invoked by uid 500); 14 Feb 2006 21:42:41 -0000 Mailing-List: contact user-help@struts.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Struts Users Mailing List" Reply-To: "Struts Users Mailing List" Delivered-To: mailing list user@struts.apache.org Received: (qmail 75423 invoked by uid 99); 14 Feb 2006 21:42:40 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Feb 2006 13:42:40 -0800 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of craigmcc@gmail.com designates 64.233.162.201 as permitted sender) Received: from [64.233.162.201] (HELO zproxy.gmail.com) (64.233.162.201) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Feb 2006 13:42:40 -0800 Received: by zproxy.gmail.com with SMTP id r28so1414367nza for ; Tue, 14 Feb 2006 13:42:19 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references; b=oVX1MahXD14FlZ2WSmlr8WuLIGa34tf1vLMtbTYDQSMyiI8MB/fiRpFwmQMQjYY9R5RhrWTwLX5P0kNSRzdoKg0DE8jNcu64xlLKNFJcO1U5SYPiJrqVILCebzoZrHG8zw9Xhoxn59eu+iO7rruv0cJJX5gMmviTMBj5a6Pnhwk= Received: by 10.64.156.14 with SMTP id d14mr2080092qbe; Tue, 14 Feb 2006 13:42:18 -0800 (PST) Received: by 10.64.253.5 with HTTP; Tue, 14 Feb 2006 13:42:18 -0800 (PST) Message-ID: Date: Tue, 14 Feb 2006 13:42:18 -0800 From: Craig McClanahan Sender: craigmcc@gmail.com To: Struts Users Mailing List Subject: Re: [SHALE] Using the Test Framework In-Reply-To: <021420061729.27315.43F2137A00012FAB00006AB322007456720A9D9B0E03020E9009@comcast.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_8126_6692894.1139953338382" References: <021420061729.27315.43F2137A00012FAB00006AB322007456720A9D9B0E03020E9009@comcast.net> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_8126_6692894.1139953338382 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 2/14/06, Gary VanMatre wrote: > > >From: "CONNER, BRENDAN (SBCSI)" > > > > OK. We're working with IBM's RSA IDE (which uses Eclipse underneath). > > I'm just trying to fit into my mind how to organize the two root source > > directories in that environment. We have a Web Project set up that > > contains the application code to be tested. Normally, we just export > > our application (including a J2EE Application project, which refers to > > Web Project(s), EJB project(s), and Java Utility project(s)) to an EAR > > file for deployment to the server, but we didn't want the test framewor= k > > stuff to be part of that export. > > > > A new feature to RSA (I guess new to eclipse 3.x) is the ability to creat= e > links outside of a project. This is pretty handy for linking in source > folders that are not under a project. Or, you could just use NetBeans :-) Seriously, NetBeans cleanly supports a parallel structure for runtime sources (src/java) and test sources (src/test). Indeed, the Shale sources themselves conform to this pattern -- take a look at the organziation of th= e "use-cases" example app, for instance. Works great, even with a freeform Ant script (as this particular directory has). It didn't even need to be a formal NB project. Craig ------=_Part_8126_6692894.1139953338382--