Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 80005 invoked from network); 19 Feb 2010 08:22:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Feb 2010 08:22:29 -0000 Received: (qmail 31132 invoked by uid 500); 19 Feb 2010 08:22:28 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 31068 invoked by uid 500); 19 Feb 2010 08:22:27 -0000 Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-java@ibatis.apache.org Delivered-To: mailing list user-java@ibatis.apache.org Received: (qmail 31060 invoked by uid 99); 19 Feb 2010 08:22:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Feb 2010 08:22:27 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of guyr-ml1@burntmail.com designates 70.87.63.122 as permitted sender) Received: from [70.87.63.122] (HELO mx02.burntmail.com) (70.87.63.122) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Feb 2010 08:22:17 +0000 Received: from pool-96-241-216-77.washdc.fios.verizon.net ([96.241.216.77] helo=[127.0.0.1]) by mx02.burntmail.com with esmtpa (Exim 4.63) (envelope-from ) id 1NiO7K-00079P-44 for user-java@ibatis.apache.org; Fri, 19 Feb 2010 02:21:42 -0600 Message-ID: <4B7E4A0F.2010404@burntmail.com> Date: Fri, 19 Feb 2010 03:21:35 -0500 From: Guy Rouillier User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: user-java@ibatis.apache.org Subject: Re: Ibator for ibatis 3 References: <20091105091750.4d233afd@dev1.cpt.ipay.co.za> <20091106074124.4b81ee4b@dev1.cpt.ipay.co.za> <4B7B907F.8050700@burntmail.com> <4B7CF70D.3000201@burntmail.com> In-Reply-To: <4B7CF70D.3000201@burntmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 100218-1, 02/18/2010), Outbound message X-Antivirus-Status: Clean X-Virus-Checked: Checked by ClamAV on apache.org After banging on this for almost 24 hrs straight, I've made some progress, but I'm stuck on an Eclipse error when I try to get the context menu on ibatorConfig.xml. I'll put the stack trace at the end because of it's length. I looked in the config and I see these two entries: /instance/org.eclipse.jdt.core/org.eclipse.jdt.core.classpathVariable.IBATOR_JAR=C\:/Program Files/Genuitec/Common/plugins/org.apache.ibatis.ibator.core_3.0.0/ibator.jar /instance/org.eclipse.jdt.core/org.eclipse.jdt.core.classpathVariable.IBATOR_JAR_SRC=C\:/Program Files/Genuitec/Common/plugins/org.apache.ibatis.ibator.core_3.0.0/ibator-src.zip Both of these are accurate, and I verified that the files at those locations contain the ibator 3.0 class files, including org.apache.ibatis.ibator.generator.XmlConstants.class. So I don't understand why I'm getting the following stack trace in the error log when I right-click. Appreciate some pointers, I'm stuck now: java.lang.Error: Unresolved compilation problems: The import org.apache.ibatis.ibator.generator cannot be resolved XmlConstants cannot be resolved at org.apache.ibatis.ibator.eclipse.ui.content.IbatorConfigVerifyer.(IbatorConfigVerifyer.java:25) at org.apache.ibatis.ibator.eclipse.ui.content.AdapterFactory.isIbatorConfigurationFile(AdapterFactory.java:85) at org.apache.ibatis.ibator.eclipse.ui.content.AdapterFactory.getAdapter(AdapterFactory.java:46) at org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:320) at org.eclipse.core.internal.runtime.AdapterManager.loadAdapter(AdapterManager.java:350) at org.eclipse.ui.internal.LegacyResourceSupport.getAdapter(LegacyResourceSupport.java:622) at org.eclipse.ui.internal.ObjectActionContributor.isApplicableTo(ObjectActionContributor.java:223) at org.eclipse.ui.internal.ObjectContributorManager.isApplicableTo(ObjectContributorManager.java:303) at org.eclipse.ui.internal.ObjectActionContributorManager.contributeObjectActions(ObjectActionContributorManager.java:83) at org.eclipse.ui.internal.PopupMenuExtender.addObjectActions(PopupMenuExtender.java:261) at org.eclipse.ui.internal.PopupMenuExtender.menuAboutToShow(PopupMenuExtender.java:337) at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:335) at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:463) at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:459) at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:485) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:235) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1008) at org.eclipse.swt.widgets.Control.WM_INITMENUPOPUP(Control.java:4111) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3815) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:337) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1576) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:1937) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4528) at org.eclipse.swt.internal.win32.OS.TrackPopupMenu(Native Method) at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:250) at org.eclipse.swt.widgets.Display.runPopups(Display.java:3849) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3416) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) On 2/18/2010 3:15 AM, Guy Rouillier wrote: > On 2/17/2010 11:00 AM, Jeff Butler wrote: >> I've learned the hard way not to make projections as to when something >> will be completed :) >> >> I need to make some updates to the Ibator documentation, and then go >> through the arduous release process - not too fun. I'm also using >> Ibator and iBATIS3 on a new project, so I have added a few new >> features to Ibator to make my own coding life easier. >> >> I can say that I'm using Ibator and iBATIS3 nearly every day for real >> work and have run into very few troubles. When will there be a new >> release? I always say "soon, hopefully". > > Thanks, as always. I just did a fresh checkout from SVN and tried to do > a build. I ran into a bit of trouble. I've not developed an Eclipse > plug-in before, so I don't really understand how all the pieces fit > together. So, I did the following: > > (1) In Eclipse, I created a new project for core, since it didn't have > one. I ran a Maven build and it completed successfully and created a > file called ibator-core-1.2.2.jar, which I copied into > eclipse/org.apache.ibatis.ibator.core/ibator.jar. > > (2) I imported projects for eclipse/core, eclipse/doc and eclipse/ui. > core and ui built automatically. But there is no task to generate the > JAR file, so I ran export. > > (3) The doc project ran into some trouble due to obsolete paths. Here > are the changes I had to make: > > > to > > > > to > > > Now buildDoc.xml completed successfully, but again no JAR was generated. > So I had to do that manually by looking at the contents of a previous > version. Amounted to creating a bin directory and copying html/*, > META-INF/*, LICENSE and NOTICE, then JARring the results. > > I haven't assembled the results into an update site yet, but I'll try > that tomorrow. Please let me know if I'm making this harder than > necessary. Would be great for the final release if all this was automatic. > > Thanks. > -- Guy Rouillier --------------------------------------------------------------------- To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org For additional commands, e-mail: user-java-help@ibatis.apache.org