From graffito-dev-return-954-apmail-incubator-graffito-dev-archive=www.apache.org@incubator.apache.org Fri Feb 03 14:46:23 2006 Return-Path: Delivered-To: apmail-incubator-graffito-dev-archive@www.apache.org Received: (qmail 26214 invoked from network); 3 Feb 2006 14:46:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Feb 2006 14:46:22 -0000 Received: (qmail 79029 invoked by uid 500); 3 Feb 2006 14:46:21 -0000 Mailing-List: contact graffito-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: graffito-dev@incubator.apache.org Delivered-To: mailing list graffito-dev@incubator.apache.org Received: (qmail 79008 invoked by uid 99); 3 Feb 2006 14:46:21 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2006 06:46:21 -0800 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: 193.19.192.5 is neither permitted nor denied by domain of the.mindstorm.mailinglist@gmail.com) Received: from [193.19.192.5] (HELO mail.evolva.ro) (193.19.192.5) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2006 06:46:20 -0800 Received: (qmail 36842 invoked by uid 1013); 3 Feb 2006 14:45:50 -0000 Received: from 86.55.40.139 by mail.evolva.ro (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87.1/1244. Clear:RC:1(86.55.40.139):. Processed in 6.308758 secs); 03 Feb 2006 14:45:50 -0000 Received: from unknown (HELO ?192.168.62.51?) (alexandru.popescu@evolva.ro@86.55.40.139) by mail.evolva.ro with AES256-SHA encrypted SMTP; 3 Feb 2006 14:45:43 -0000 Message-ID: <43E36C8F.9030600@gmail.com> Date: Fri, 03 Feb 2006 16:45:35 +0200 From: Alexandru Popescu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051201 Thunderbird/1.5 Mnenhy/0.7.3.0 MIME-Version: 1.0 To: graffito-dev@incubator.apache.org Subject: Re: problems trying to run test units References: <43E15A6A.5040001@gmail.com> <43E15DAE.1030901@gmail.com> <3b728ee90602020036s12f7b9daqc29cdd8631993c37@mail.gmail.com> <43E1EEE1.7090304@gmail.com> <3b728ee90602020450q6eb8c41g5a8784243ad1dbf2@mail.gmail.com> <43E244AE.30405@gmail.com> <3b728ee90602021135h2eb37c66sd17de36c5f711373@mail.gmail.com> In-Reply-To: <3b728ee90602021135h2eb37c66sd17de36c5f711373@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi! Thanks for the explanation about how it works. Considering that I had problems running the suite from withing the IDE, I have modified the base test to use the Jackrabbit API to import custom nodes. Considering that there is no specification to handle custom node types, I would say that both solutions are oke. The single difference is that the programmatic approach (the way i have modified the base test) will allow running the suite from within the IDE. ./alex -- .w( the_mindstorm )p. #: Christophe Lombart changed the world a bit at a time by saying (astral date: 2/2/2006 9:35 PM) :# > For unit test, the custom node type file solution is quite easy. > of course, for real applications I see good reasons to use the API to > import the node types. > > How is it working for the unit tests ? (see the maven.xml, it is > quite simple to understand) : > > 1/ Node types used in the unit tests are added in : > /src/test-config/repository/repository/nodetypes/custom_nodetypes.xml > > 2/ target/repository contains the repository for the unit test and can > clean up with " maven clean" . > > 3/ before starting the unit tests, > /src/test-config/repository/repository/nodetypes/custom_nodetypes.xml > is copied into target/repository/repository/nodetypes > > > of course, we have the same result by using the API but I didn't know > that Oliver has finished that. Up to you to choose what you want. > > > > On 2/2/06, Oliver Kiessler wrote: >> > That's how I have modified the BaseTest to do ;-). Register the custom node types using Jackrabbit >> > API (before Christophe explaining how it works with Maven). >> >> sorry about that! I didn't know... Well, both ways are possible but I >> prefer solving this programmatically.... ;) >> >> - oliver >> > > > -- > Best regards, > > Christophe >