Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 25382 invoked from network); 6 Nov 2009 21:49:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Nov 2009 21:49:35 -0000 Received: (qmail 31779 invoked by uid 500); 6 Nov 2009 21:49:35 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 31698 invoked by uid 500); 6 Nov 2009 21:49:35 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 31689 invoked by uid 99); 6 Nov 2009 21:49:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Nov 2009 21:49:35 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [87.241.53.234] (HELO silmasoftware.com) (87.241.53.234) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Nov 2009 21:49:24 +0000 Received: from WorldClient by silmasoftware.com (MDaemon.Standard.v8.1.3.R) with ESMTP id md50000922420.msg for ; Fri, 06 Nov 2009 21:45:48 +0100 Received: from [93.35.123.121] via WorldClient with HTTP; Fri, 06 Nov 2009 21:45:47 +0100 Date: Fri, 06 Nov 2009 21:45:47 +0100 From: "flavio palumbo" To: "Derby Discussion" Subject: Re: R: using ASTParser and TreeWalker MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Message-ID: X-Mailer: WorldClient 8.1.3 In-Reply-To: <4AF4505A.9090203@sun.com> References: <4AF4505A.9090203@sun.com> X-Authenticated-Sender: f.palumbo@silmasoftware.com X-MDRemoteIP: 127.0.0.1 X-Return-Path: f.palumbo@silmasoftware.com X-MDaemon-Deliver-To: derby-user@db.apache.org X-Virus-Checked: Checked by ClamAV on apache.org Hi Rich, I've just tried to build Derby (now I'm at home with nb 6.5.1 on win vista) and got these messages : ..... ..... Building zip: D:\derby2009\trunk\java\demo\toursdb\toursdb.jar Finished building toursdb copyfiles: Copying 13 files to D:\derby2009\trunk\classes\org\apache\derbyTesting\functionTests\tests\demo toursdb: demo: testing: testing: junitcomponents: Compiling 1 source file to D:\derby2009\trunk\classes D:\derby2009\trunk\java\testing\org\apache\derbyTesting\junit\SecurityManagerSetup.java:30: package junit.extensions does not exist import junit.extensions.TestSetup; D:\derby2009\trunk\java\testing\org\apache\derbyTesting\junit\SecurityManagerSetup.java:31: package junit.framework does not exist import junit.framework.Test; D:\derby2009\trunk\java\testing\org\apache\derbyTesting\junit\SecurityManagerSetup.java:32: package junit.framework does not exist import junit.framework.TestSuite; D:\derby2009\trunk\java\testing\org\apache\derbyTesting\junit\SecurityManagerSetup.java:39: cannot find symbol symbol: class TestSetup public final class SecurityManagerSetup extends TestSetup { D:\derby2009\trunk\java\testing\org\apache\derbyTesting\junit\SecurityManagerSetup.java:73: cannot find symbol symbol : class Test location: class org.apache.derbyTesting.junit.SecurityManagerSetup public SecurityManagerSetup(Test test, String policyResource) ^ D:\derby2009\trunk\java\testing\org\apache\derbyTesting\junit\SecurityManagerSetup.java:94: cannot find symbol symbol : class Test location: class org.apache.derbyTesting.junit.SecurityManagerSetup public static Test noSecurityManager(Test test) ^ D:\derby2009\trunk\java\testing\org\apache\derbyTesting\junit\SecurityManagerSetup.java:94: cannot find symbol symbol : class Test location: class org.apache.derbyTesting.junit.SecurityManagerSetup public static Test noSecurityManager(Test test) ..... ..... D:\derby2009\trunk\java\testing\org\apache\derbyTesting\junit\JDBC.java:673: cannot find symbol symbol : variable Assert location: class org.apache.derbyTesting.junit.JDBC Assert.assertEquals("Unexpected column count:", 100 errors D:\derby2009\trunk\build.xml:499: The following error occurred while executing this line: D:\derby2009\trunk\java\testing\build.xml:59: The following error occurred while executing this line: D:\derby2009\trunk\java\testing\org\apache\derbyTesting\junit\build.xml:74: Compile failed; see the compiler error output for details. BUILD FAILED (total time: 54 seconds) The previous time I hadn't read carefully the building.html doc, but now I've put ant.jar and junit-3.8.2.jar into my D:\derby2009\trunk\tools\java directory. It seems that nothing has changed :-(( Thanks a lot Flavio -----Original Message----- From: Rick Hillegas To: Derby Discussion Date: Fri, 06 Nov 2009 08:35:38 -0800 Subject: Re: R: using ASTParser and TreeWalker > Hi Flavio, > > A couple more comments inline... > > Flavio Palumbo wrote: > > Hi Rich, > > > > thanks for your super quick answer ;-)) > > > > > >> Please tell us more about the problems you are having compiling the > >> Derby trunk. We want to make the build easier. > >> > > > > I tried to build Derby following the guide at > > http://wiki.apache.org/db-derby/BuildingDerby ; I'm currently using > NetBeans > > 6.5 with jdk 1.6.0 ; when I try to build the project I get a lot of > > exceptions due mainly to the fact that I'm not able to add jUnit jars > to the > > project. > > I'm bit hurry now, I'll try to generate again the project this week > end to > > be more accurate. > > > Thanks for giving us this feedback. If you configure the ant build > target to be "buildsource" rather than "all", then you shouldn't need > the junit jars. For more information, see the BUILDING.html file in the > root directory of the Derby trunk. > > > >> Yes, you should be able to compile these classes against the > official > >> debug jars for 10.5.3.0. > >> > > > > what you mean with "debug jars" ? > > > If you go to the 10.5.3 download page ( > http://db.apache.org/derby/releases/release-10.5.3.0.cgi ), you'll see > a > number of downloadable distributions. Two of them have the word "debug" > in their names. The jars in those two distributions have extra tracing > logic built into them. The TreeWalker uses that extra tracing logic. > > Hope this helps, > -Rick > > Thanks a lot. > > > > Flavio > > > > > > > >> -----Messaggio originale----- > >> Da: Richard.Hillegas@Sun.COM [mailto:Richard.Hillegas@Sun.COM] > >> Inviato: venerd� 6 novembre 2009 15.45 > >> A: Derby Discussion > >> Oggetto: Re: using ASTParser and TreeWalker > >> > >> > >> Hi Flavio, > >> > >> Flavio Palumbo wrote: > >> > >>> Hi all, > >>> > >>> I tried test ASTParser and TreeWalker to try to parse SQL > >>> > >> strings and the > >> > >>> first works fine while I cannot compile the second cause I receive > this > >>> compile time error : > >>> TreeWalker is not abstract and does not override abstract method > >>> visitChildrenFirst(org.apache.derby.iapi.sql.compile.Visitable) in > >>> org.apache.derby.iapi.sql.compile.Visitor > >>> > >>> is there a newer version I can use or can somebody tell me how > >>> > >> to fix this > >> > >>> problem ? > >>> > >>> > >> The visitChildrenFirst() method was added to the Visitor interface > >> recently. I have attached new versions of TreeWalker, > XmlTreeWalker, > >> and XmlTreePrinter to DERBY-3946, DERBY-791, and DERBY-4415 > >> respectively. The new versions implement the new method and should > >> compile against the current Derby trunk. If this doesn't fix your > >> problem, let me know and I'll look into this more. > >> > >>> also I found the post "Rick Hillegas added a comment - > >>> > >> 25/Aug/09 04:00 PM" > >> > >>> on https://issues.apache.org/jira/browse/DERBY-3946 : > >>> > >>> I have successfully compiled and run this ASTParser against the > debug > >>> derby.jar that is part of the 10.5.3.0 distribution > >>> > >>> it means that I can compile and run ASTParser and TreeWalker > against the > >>> normal distribution of Derby ? > >>> > >>> > >> Yes, you should be able to compile these classes against the > official > >> debug jars for 10.5.3.0. > >> > >>> this would be great cause I fight a lot to compile Derby from svn. > >>> > >>> > >> Please tell us more about the problems you are having compiling the > >> Derby trunk. We want to make the build easier. > >> > >> Thanks, > >> -Rick > >> > >>> Any hint would be appreciated. > >>> > >>> Flavio > >>> > >>> > >>> ----------------------------------------------------------- > >>> Il presente messaggio non costituisce un impegno contrattuale > >>> > >> tra SILMA S.r.l. ed il destinatario. > >> > >>> Le opinioni ivi espresse sono quelle dell'autore. > >>> SILMA S.r.l. non assume alcuna responsabilita riguardo al > >>> > >> contenuto del presente messaggio. > >> > >>> Il messaggio � destinato esclusivamente al destinatario. > >>> Il contenuto e gli allegati sono da considerarsi di natura > confidenziale > >>> > >>> Nel caso abbiate ricevuto il presente messaggio per errore > >>> > >> siete pregati di comunicarlo > >> > >>> alla casella segreteria@silmasoftware.com. > >>> > >>> > >>> > > > > > > ----------------------------------------------------------- > > Il presente messaggio non costituisce un impegno contrattuale tra > SILMA S.r.l. ed il destinatario. > > Le opinioni ivi espresse sono quelle dell'autore. > > SILMA S.r.l. non assume alcuna responsabilita riguardo al contenuto > del presente messaggio. > > Il messaggio � destinato esclusivamente al destinatario. > > Il contenuto e gli allegati sono da considerarsi di natura > confidenziale > > > > Nel caso abbiate ricevuto il presente messaggio per errore siete > pregati di comunicarlo > > alla casella segreteria@silmasoftware.com. > > > > ----------------------------------------------------------- Il presente messaggio non costituisce un impegno contrattuale tra SILMA S.r.l. ed il destinatario. Le opinioni ivi espresse sono quelle dell'autore. SILMA S.r.l. non assume alcuna responsabilita riguardo al contenuto del presente messaggio. Il messaggio � destinato esclusivamente al destinatario. Il contenuto e gli allegati sono da considerarsi di natura confidenziale Nel caso abbiate ricevuto il presente messaggio per errore siete pregati di comunicarlo alla casella segreteria@silmasoftware.com.