You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user-java@ibatis.apache.org by Zach Visagie <za...@ipay.co.za> on 2009/11/05 08:17:50 UTC
Ibator for ibatis 3
Hi
My comment: I have had a first look at ibatis 3 and I like it a lot. Even though annotations might not have lived up to the expected promise, we certainly have some use cases for which they are going to be very handy. Thanks for the good work guys! (I can soon retire my custom auto generated keys hack for ibatis 2)
My question: We have a new project we will be working on for the next 5-7 months and I want to start using ibatis 3 and ibator. Is there any ibator code for ibatis 3 in svn that can be checked out or any binaries for a current version of ibator that supports ibatis 3?
thanks
Zach
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org
Re: Ibator for ibatis 3
Posted by Jeff Butler <je...@gmail.com>.
Hi Guy,
The Eclipse plugin build is undergoing lots of changes right now.
Thanks for the reminder about the MANIFEST.MF versions - I definitely
need to change those.
The <includes> section is there because I'm changing the build to use
a headless PDE build rather than using the site generate feature.
This will allow me to publish source bundles for the plugins -
something I've never done before. You might notice that there is a
new "build" project in SVN - there's an Ant script there that builds
the plugin now.
I'll clean up site.xml once everything else is working. They seem to
change the format of site.xml with every release of eclipse :)
As with all things eclipse, the platform is overwhelming and it's
taking me a long time to piece the build together from arcane bits of
information on WIKIs and blogs. It's *almost* working now - I should
have it complete in another day or two. Then maybe I can do a real
release next weekend.
Jeff
On Sun, Feb 21, 2010 at 10:15 PM, Guy Rouillier <gu...@burntmail.com> wrote:
> Jeff, I did a fresh checkout and build, and I'm now able to use the Ibator
> Eclipse feature. Much thanks for making the needed changes. I had to make
> some small changes to get everything to work:
>
> MANIFEST.MF for ui plug-in:
>
> Update the following two lines:
>
> org.apache.ibatis.ibator.eclipse.core;bundle-version="1.2.2",
> org.apache.ibatis.ibator.core;bundle-version="1.2.2",
>
> feature.xml:
>
> delete:
> <includes
> id="org.apache.ibatis.ibator.source"
> version="0.0.0"/>
>
> site.xml:
>
> delete:
> <feature url="features/org.apache.ibatis.ibator_1.2.0.jar"
> id="org.apache.ibatis.ibator" version="1.2.0">
> <category name="Ibator Version 1.2"/>
> </feature>
> <feature url="features/org.apache.ibatis.ibator_1.2.1.jar"
> id="org.apache.ibatis.ibator" version="1.2.1">
> <category name="Ibator Version 1.2"/>
> </feature>
>
> I generated an update site to share with co-workers. If I didn't delete
> these, then when I added the Update Site, Eclipse showed me 3 entries for
> the Ibator feature, and the titles were the same for all, since the title
> comes from the category name.
>
> One other issue I noticed was that when I instructed Eclipse to remove this
> feature, it did not delete the JAR files. That caused problems on the next
> install. So what I ended up doing was to delete the feature, shut down
> Eclipse, manually delete the JAR files, restart Eclipse and reinstall the
> feature.
>
>
> On 2/19/2010 6:47 PM, Guy Rouillier wrote:
>>
>> I'll try a fresh checkout. The link below is failing for me:
>>
>> The requested URL
>>
>> /repos/asf/ibatis/java/ibator/trunk/eclipse/org.apacheibatis.ibator.eclipse.doc/html-src/eclipseui/buildingFromSVN.html
>> was not found on this server.
>>
>> On 2/19/2010 4:07 PM, Jeff Butler wrote:
>>>
>>> I just committed some changes to the eclipse plugin code for version
>>> 1.2.2. Things work fine for me. Also, I updated the instructions for
>>> building the eclipse plugin here:
>>>
>>>
>>> http://svn.apache.org/repos/asf/ibatis/java/ibator/trunk/eclipse/org.apacheibatis.ibator.eclipse.doc/html-src/eclipseui/buildingFromSVN.html
>>>
>>>
>>> Jeff Butler
>>>
>>>
>>> On Fri, Feb 19, 2010 at 12:31 PM, Guy
>>> Rouillier<gu...@burntmail.com> wrote:
>>>>
>>>> Unfortunately, that's not it. I had found that manifest and updated
>>>> it to
>>>> reflect 3.0.0. I'll try working more on this tonight. I'll search my
>>>> Eclipse installation and just remove all other instances of the
>>>> Ibator JAR;
>>>> hopefully then at least Eclipse will give me some big error message
>>>> identifying where it is picking up the older version. Thanks.
>>>>
>>>> ========
>>>> Manifest-Version: 1.0
>>>> Bundle-ManifestVersion: 2
>>>> Bundle-Name: Ibator Core Plug-in
>>>> Bundle-SymbolicName: org.apache.ibatis.ibator.core
>>>> Bundle-Version: 3.0.0
>>>> Bundle-ClassPath: ibator.jar
>>>> Export-Package: org.apache.ibatis.ibator.ant,
>>>> org.apache.ibatis.ibator.api,
>>>> org.apache.ibatis.ibator.api.dom,
>>>> org.apache.ibatis.ibator.api.dom.java,
>>>> org.apache.ibatis.ibator.api.dom.xml,
>>>> org.apache.ibatis.ibator.config,
>>>> org.apache.ibatis.ibator.config.xml,
>>>> org.apache.ibatis.ibator.exception,
>>>> org.apache.ibatis.ibator.generator,
>>>> org.apache.ibatis.ibator.generator.ibatis2,
>>>> org.apache.ibatis.ibator.generator.ibatis2.dao,
>>>> org.apache.ibatis.ibator.generator.ibatis2.dao.elements,
>>>> org.apache.ibatis.ibator.generator.ibatis2.dao.templates,
>>>> org.apache.ibatis.ibator.generator.ibatis2.model,
>>>> org.apache.ibatis.ibator.generator.ibatis2.sqlmap,
>>>> org.apache.ibatis.ibator.generator.ibatis2.sqlmap.elements,
>>>> org.apache.ibatis.ibator.generator.ibatis3,
>>>> org.apache.ibatis.ibator.generator.ibatis3.javamapper,
>>>> org.apache.ibatis.ibator.generator.ibatis3.javamapper.elements,
>>>> org.apache.ibatis.ibator.generator.ibatis3.model,
>>>> org.apache.ibatis.ibator.generator.ibatis3.xmlmapper,
>>>> org.apache.ibatis.ibator.generator.ibatis3.xmlmapper.elements,
>>>> org.apache.ibatis.ibator.internal,
>>>> org.apache.ibatis.ibator.internal.db,
>>>> org.apache.ibatis.ibator.internal.rules,
>>>> org.apache.ibatis.ibator.internal.types,
>>>> org.apache.ibatis.ibator.internal.util,
>>>> org.apache.ibatis.ibator.internal.util.messages,
>>>> org.apache.ibatis.ibator.logging,
>>>> org.apache.ibatis.ibator.maven,
>>>> org.apache.ibatis.ibator.plugins
>>>> Bundle-RequiredExecutionEnvironment: J2SE-1.5
>>>> =========
>>>>
>>>>
>>>> On 2/19/2010 9:22 AM, Jeff Butler wrote:
>>>>>
>>>>> Look at MANIFEST.MF in the ibator.core project. The Export-Package
>>>>> directive must list all packages in the ibator.jar file - the version
>>>>> in SVN needs an update.
>>>>>
>>>>> A small bit of OSGI loveliness. That's my best guess. I'll take a
>>>>> look at updating this in SVN later today - hopefully :)
>>>>>
>>>>> Jeff Butler
>>>>>
>>>>>
>>>>> On Fri, Feb 19, 2010 at 2:21 AM, Guy Rouillier<gu...@burntmail.com>
>>>>> wrote:
>>>>>>
>>>>>> 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.<init>(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:
>>>>>>>
>>>>>>> <packageset dir="../../core/src" />
>>>>>>> to
>>>>>>> <packageset dir="../../core/ibator-core/src" />
>>>>>>>
>>>>>>> <fileset dir="../../core/htmldoc">
>>>>>>> to
>>>>>>> <fileset dir="../../core/ibator-core/doc/html">
>>>>>>>
>>>>>>> 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
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
>>>>> For additional commands, e-mail: user-java-help@ibatis.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Guy Rouillier
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
>>>> For additional commands, e-mail: user-java-help@ibatis.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
>>> For additional commands, e-mail: user-java-help@ibatis.apache.org
>>>
>>>
>>
>>
>
>
> --
> Guy Rouillier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
> For additional commands, e-mail: user-java-help@ibatis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org
Re: Ibator for ibatis 3
Posted by Guy Rouillier <gu...@burntmail.com>.
Jeff, I did a fresh checkout and build, and I'm now able to use the
Ibator Eclipse feature. Much thanks for making the needed changes. I
had to make some small changes to get everything to work:
MANIFEST.MF for ui plug-in:
Update the following two lines:
org.apache.ibatis.ibator.eclipse.core;bundle-version="1.2.2",
org.apache.ibatis.ibator.core;bundle-version="1.2.2",
feature.xml:
delete:
<includes
id="org.apache.ibatis.ibator.source"
version="0.0.0"/>
site.xml:
delete:
<feature url="features/org.apache.ibatis.ibator_1.2.0.jar"
id="org.apache.ibatis.ibator" version="1.2.0">
<category name="Ibator Version 1.2"/>
</feature>
<feature url="features/org.apache.ibatis.ibator_1.2.1.jar"
id="org.apache.ibatis.ibator" version="1.2.1">
<category name="Ibator Version 1.2"/>
</feature>
I generated an update site to share with co-workers. If I didn't delete
these, then when I added the Update Site, Eclipse showed me 3 entries
for the Ibator feature, and the titles were the same for all, since the
title comes from the category name.
One other issue I noticed was that when I instructed Eclipse to remove
this feature, it did not delete the JAR files. That caused problems on
the next install. So what I ended up doing was to delete the feature,
shut down Eclipse, manually delete the JAR files, restart Eclipse and
reinstall the feature.
On 2/19/2010 6:47 PM, Guy Rouillier wrote:
> I'll try a fresh checkout. The link below is failing for me:
>
> The requested URL
> /repos/asf/ibatis/java/ibator/trunk/eclipse/org.apacheibatis.ibator.eclipse.doc/html-src/eclipseui/buildingFromSVN.html
> was not found on this server.
>
> On 2/19/2010 4:07 PM, Jeff Butler wrote:
>> I just committed some changes to the eclipse plugin code for version
>> 1.2.2. Things work fine for me. Also, I updated the instructions for
>> building the eclipse plugin here:
>>
>> http://svn.apache.org/repos/asf/ibatis/java/ibator/trunk/eclipse/org.apacheibatis.ibator.eclipse.doc/html-src/eclipseui/buildingFromSVN.html
>>
>>
>> Jeff Butler
>>
>>
>> On Fri, Feb 19, 2010 at 12:31 PM, Guy
>> Rouillier<gu...@burntmail.com> wrote:
>>> Unfortunately, that's not it. I had found that manifest and updated
>>> it to
>>> reflect 3.0.0. I'll try working more on this tonight. I'll search my
>>> Eclipse installation and just remove all other instances of the
>>> Ibator JAR;
>>> hopefully then at least Eclipse will give me some big error message
>>> identifying where it is picking up the older version. Thanks.
>>>
>>> ========
>>> Manifest-Version: 1.0
>>> Bundle-ManifestVersion: 2
>>> Bundle-Name: Ibator Core Plug-in
>>> Bundle-SymbolicName: org.apache.ibatis.ibator.core
>>> Bundle-Version: 3.0.0
>>> Bundle-ClassPath: ibator.jar
>>> Export-Package: org.apache.ibatis.ibator.ant,
>>> org.apache.ibatis.ibator.api,
>>> org.apache.ibatis.ibator.api.dom,
>>> org.apache.ibatis.ibator.api.dom.java,
>>> org.apache.ibatis.ibator.api.dom.xml,
>>> org.apache.ibatis.ibator.config,
>>> org.apache.ibatis.ibator.config.xml,
>>> org.apache.ibatis.ibator.exception,
>>> org.apache.ibatis.ibator.generator,
>>> org.apache.ibatis.ibator.generator.ibatis2,
>>> org.apache.ibatis.ibator.generator.ibatis2.dao,
>>> org.apache.ibatis.ibator.generator.ibatis2.dao.elements,
>>> org.apache.ibatis.ibator.generator.ibatis2.dao.templates,
>>> org.apache.ibatis.ibator.generator.ibatis2.model,
>>> org.apache.ibatis.ibator.generator.ibatis2.sqlmap,
>>> org.apache.ibatis.ibator.generator.ibatis2.sqlmap.elements,
>>> org.apache.ibatis.ibator.generator.ibatis3,
>>> org.apache.ibatis.ibator.generator.ibatis3.javamapper,
>>> org.apache.ibatis.ibator.generator.ibatis3.javamapper.elements,
>>> org.apache.ibatis.ibator.generator.ibatis3.model,
>>> org.apache.ibatis.ibator.generator.ibatis3.xmlmapper,
>>> org.apache.ibatis.ibator.generator.ibatis3.xmlmapper.elements,
>>> org.apache.ibatis.ibator.internal,
>>> org.apache.ibatis.ibator.internal.db,
>>> org.apache.ibatis.ibator.internal.rules,
>>> org.apache.ibatis.ibator.internal.types,
>>> org.apache.ibatis.ibator.internal.util,
>>> org.apache.ibatis.ibator.internal.util.messages,
>>> org.apache.ibatis.ibator.logging,
>>> org.apache.ibatis.ibator.maven,
>>> org.apache.ibatis.ibator.plugins
>>> Bundle-RequiredExecutionEnvironment: J2SE-1.5
>>> =========
>>>
>>>
>>> On 2/19/2010 9:22 AM, Jeff Butler wrote:
>>>>
>>>> Look at MANIFEST.MF in the ibator.core project. The Export-Package
>>>> directive must list all packages in the ibator.jar file - the version
>>>> in SVN needs an update.
>>>>
>>>> A small bit of OSGI loveliness. That's my best guess. I'll take a
>>>> look at updating this in SVN later today - hopefully :)
>>>>
>>>> Jeff Butler
>>>>
>>>>
>>>> On Fri, Feb 19, 2010 at 2:21 AM, Guy Rouillier<gu...@burntmail.com>
>>>> wrote:
>>>>>
>>>>> 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.<init>(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:
>>>>>>
>>>>>> <packageset dir="../../core/src" />
>>>>>> to
>>>>>> <packageset dir="../../core/ibator-core/src" />
>>>>>>
>>>>>> <fileset dir="../../core/htmldoc">
>>>>>> to
>>>>>> <fileset dir="../../core/ibator-core/doc/html">
>>>>>>
>>>>>> 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
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
>>>> For additional commands, e-mail: user-java-help@ibatis.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Guy Rouillier
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
>>> For additional commands, e-mail: user-java-help@ibatis.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
>> For additional commands, e-mail: user-java-help@ibatis.apache.org
>>
>>
>
>
--
Guy Rouillier
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org
Re: Ibator for ibatis 3
Posted by Guy Rouillier <gu...@burntmail.com>.
I'll try a fresh checkout. The link below is failing for me:
The requested URL
/repos/asf/ibatis/java/ibator/trunk/eclipse/org.apacheibatis.ibator.eclipse.doc/html-src/eclipseui/buildingFromSVN.html
was not found on this server.
On 2/19/2010 4:07 PM, Jeff Butler wrote:
> I just committed some changes to the eclipse plugin code for version
> 1.2.2. Things work fine for me. Also, I updated the instructions for
> building the eclipse plugin here:
>
> http://svn.apache.org/repos/asf/ibatis/java/ibator/trunk/eclipse/org.apacheibatis.ibator.eclipse.doc/html-src/eclipseui/buildingFromSVN.html
>
> Jeff Butler
>
>
> On Fri, Feb 19, 2010 at 12:31 PM, Guy Rouillier<gu...@burntmail.com> wrote:
>> Unfortunately, that's not it. I had found that manifest and updated it to
>> reflect 3.0.0. I'll try working more on this tonight. I'll search my
>> Eclipse installation and just remove all other instances of the Ibator JAR;
>> hopefully then at least Eclipse will give me some big error message
>> identifying where it is picking up the older version. Thanks.
>>
>> ========
>> Manifest-Version: 1.0
>> Bundle-ManifestVersion: 2
>> Bundle-Name: Ibator Core Plug-in
>> Bundle-SymbolicName: org.apache.ibatis.ibator.core
>> Bundle-Version: 3.0.0
>> Bundle-ClassPath: ibator.jar
>> Export-Package: org.apache.ibatis.ibator.ant,
>> org.apache.ibatis.ibator.api,
>> org.apache.ibatis.ibator.api.dom,
>> org.apache.ibatis.ibator.api.dom.java,
>> org.apache.ibatis.ibator.api.dom.xml,
>> org.apache.ibatis.ibator.config,
>> org.apache.ibatis.ibator.config.xml,
>> org.apache.ibatis.ibator.exception,
>> org.apache.ibatis.ibator.generator,
>> org.apache.ibatis.ibator.generator.ibatis2,
>> org.apache.ibatis.ibator.generator.ibatis2.dao,
>> org.apache.ibatis.ibator.generator.ibatis2.dao.elements,
>> org.apache.ibatis.ibator.generator.ibatis2.dao.templates,
>> org.apache.ibatis.ibator.generator.ibatis2.model,
>> org.apache.ibatis.ibator.generator.ibatis2.sqlmap,
>> org.apache.ibatis.ibator.generator.ibatis2.sqlmap.elements,
>> org.apache.ibatis.ibator.generator.ibatis3,
>> org.apache.ibatis.ibator.generator.ibatis3.javamapper,
>> org.apache.ibatis.ibator.generator.ibatis3.javamapper.elements,
>> org.apache.ibatis.ibator.generator.ibatis3.model,
>> org.apache.ibatis.ibator.generator.ibatis3.xmlmapper,
>> org.apache.ibatis.ibator.generator.ibatis3.xmlmapper.elements,
>> org.apache.ibatis.ibator.internal,
>> org.apache.ibatis.ibator.internal.db,
>> org.apache.ibatis.ibator.internal.rules,
>> org.apache.ibatis.ibator.internal.types,
>> org.apache.ibatis.ibator.internal.util,
>> org.apache.ibatis.ibator.internal.util.messages,
>> org.apache.ibatis.ibator.logging,
>> org.apache.ibatis.ibator.maven,
>> org.apache.ibatis.ibator.plugins
>> Bundle-RequiredExecutionEnvironment: J2SE-1.5
>> =========
>>
>>
>> On 2/19/2010 9:22 AM, Jeff Butler wrote:
>>>
>>> Look at MANIFEST.MF in the ibator.core project. The Export-Package
>>> directive must list all packages in the ibator.jar file - the version
>>> in SVN needs an update.
>>>
>>> A small bit of OSGI loveliness. That's my best guess. I'll take a
>>> look at updating this in SVN later today - hopefully :)
>>>
>>> Jeff Butler
>>>
>>>
>>> On Fri, Feb 19, 2010 at 2:21 AM, Guy Rouillier<gu...@burntmail.com>
>>> wrote:
>>>>
>>>> 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.<init>(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:
>>>>>
>>>>> <packageset dir="../../core/src" />
>>>>> to
>>>>> <packageset dir="../../core/ibator-core/src" />
>>>>>
>>>>> <fileset dir="../../core/htmldoc">
>>>>> to
>>>>> <fileset dir="../../core/ibator-core/doc/html">
>>>>>
>>>>> 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
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
>>> For additional commands, e-mail: user-java-help@ibatis.apache.org
>>>
>>>
>>
>>
>> --
>> Guy Rouillier
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
>> For additional commands, e-mail: user-java-help@ibatis.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
> For additional commands, e-mail: user-java-help@ibatis.apache.org
>
>
--
Guy Rouillier
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org
Re: Ibator for ibatis 3
Posted by Jeff Butler <je...@gmail.com>.
I just committed some changes to the eclipse plugin code for version
1.2.2. Things work fine for me. Also, I updated the instructions for
building the eclipse plugin here:
http://svn.apache.org/repos/asf/ibatis/java/ibator/trunk/eclipse/org.apache.ibatis.ibator.eclipse.doc/html-src/eclipseui/buildingFromSVN.html
Jeff Butler
On Fri, Feb 19, 2010 at 12:31 PM, Guy Rouillier <gu...@burntmail.com> wrote:
> Unfortunately, that's not it. I had found that manifest and updated it to
> reflect 3.0.0. I'll try working more on this tonight. I'll search my
> Eclipse installation and just remove all other instances of the Ibator JAR;
> hopefully then at least Eclipse will give me some big error message
> identifying where it is picking up the older version. Thanks.
>
> ========
> Manifest-Version: 1.0
> Bundle-ManifestVersion: 2
> Bundle-Name: Ibator Core Plug-in
> Bundle-SymbolicName: org.apache.ibatis.ibator.core
> Bundle-Version: 3.0.0
> Bundle-ClassPath: ibator.jar
> Export-Package: org.apache.ibatis.ibator.ant,
> org.apache.ibatis.ibator.api,
> org.apache.ibatis.ibator.api.dom,
> org.apache.ibatis.ibator.api.dom.java,
> org.apache.ibatis.ibator.api.dom.xml,
> org.apache.ibatis.ibator.config,
> org.apache.ibatis.ibator.config.xml,
> org.apache.ibatis.ibator.exception,
> org.apache.ibatis.ibator.generator,
> org.apache.ibatis.ibator.generator.ibatis2,
> org.apache.ibatis.ibator.generator.ibatis2.dao,
> org.apache.ibatis.ibator.generator.ibatis2.dao.elements,
> org.apache.ibatis.ibator.generator.ibatis2.dao.templates,
> org.apache.ibatis.ibator.generator.ibatis2.model,
> org.apache.ibatis.ibator.generator.ibatis2.sqlmap,
> org.apache.ibatis.ibator.generator.ibatis2.sqlmap.elements,
> org.apache.ibatis.ibator.generator.ibatis3,
> org.apache.ibatis.ibator.generator.ibatis3.javamapper,
> org.apache.ibatis.ibator.generator.ibatis3.javamapper.elements,
> org.apache.ibatis.ibator.generator.ibatis3.model,
> org.apache.ibatis.ibator.generator.ibatis3.xmlmapper,
> org.apache.ibatis.ibator.generator.ibatis3.xmlmapper.elements,
> org.apache.ibatis.ibator.internal,
> org.apache.ibatis.ibator.internal.db,
> org.apache.ibatis.ibator.internal.rules,
> org.apache.ibatis.ibator.internal.types,
> org.apache.ibatis.ibator.internal.util,
> org.apache.ibatis.ibator.internal.util.messages,
> org.apache.ibatis.ibator.logging,
> org.apache.ibatis.ibator.maven,
> org.apache.ibatis.ibator.plugins
> Bundle-RequiredExecutionEnvironment: J2SE-1.5
> =========
>
>
> On 2/19/2010 9:22 AM, Jeff Butler wrote:
>>
>> Look at MANIFEST.MF in the ibator.core project. The Export-Package
>> directive must list all packages in the ibator.jar file - the version
>> in SVN needs an update.
>>
>> A small bit of OSGI loveliness. That's my best guess. I'll take a
>> look at updating this in SVN later today - hopefully :)
>>
>> Jeff Butler
>>
>>
>> On Fri, Feb 19, 2010 at 2:21 AM, Guy Rouillier<gu...@burntmail.com>
>> wrote:
>>>
>>> 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.<init>(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:
>>>>
>>>> <packageset dir="../../core/src" />
>>>> to
>>>> <packageset dir="../../core/ibator-core/src" />
>>>>
>>>> <fileset dir="../../core/htmldoc">
>>>> to
>>>> <fileset dir="../../core/ibator-core/doc/html">
>>>>
>>>> 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
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
>> For additional commands, e-mail: user-java-help@ibatis.apache.org
>>
>>
>
>
> --
> Guy Rouillier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
> For additional commands, e-mail: user-java-help@ibatis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org
Re: Ibator for ibatis 3
Posted by Guy Rouillier <gu...@burntmail.com>.
Unfortunately, that's not it. I had found that manifest and updated it
to reflect 3.0.0. I'll try working more on this tonight. I'll search
my Eclipse installation and just remove all other instances of the
Ibator JAR; hopefully then at least Eclipse will give me some big error
message identifying where it is picking up the older version. Thanks.
========
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Ibator Core Plug-in
Bundle-SymbolicName: org.apache.ibatis.ibator.core
Bundle-Version: 3.0.0
Bundle-ClassPath: ibator.jar
Export-Package: org.apache.ibatis.ibator.ant,
org.apache.ibatis.ibator.api,
org.apache.ibatis.ibator.api.dom,
org.apache.ibatis.ibator.api.dom.java,
org.apache.ibatis.ibator.api.dom.xml,
org.apache.ibatis.ibator.config,
org.apache.ibatis.ibator.config.xml,
org.apache.ibatis.ibator.exception,
org.apache.ibatis.ibator.generator,
org.apache.ibatis.ibator.generator.ibatis2,
org.apache.ibatis.ibator.generator.ibatis2.dao,
org.apache.ibatis.ibator.generator.ibatis2.dao.elements,
org.apache.ibatis.ibator.generator.ibatis2.dao.templates,
org.apache.ibatis.ibator.generator.ibatis2.model,
org.apache.ibatis.ibator.generator.ibatis2.sqlmap,
org.apache.ibatis.ibator.generator.ibatis2.sqlmap.elements,
org.apache.ibatis.ibator.generator.ibatis3,
org.apache.ibatis.ibator.generator.ibatis3.javamapper,
org.apache.ibatis.ibator.generator.ibatis3.javamapper.elements,
org.apache.ibatis.ibator.generator.ibatis3.model,
org.apache.ibatis.ibator.generator.ibatis3.xmlmapper,
org.apache.ibatis.ibator.generator.ibatis3.xmlmapper.elements,
org.apache.ibatis.ibator.internal,
org.apache.ibatis.ibator.internal.db,
org.apache.ibatis.ibator.internal.rules,
org.apache.ibatis.ibator.internal.types,
org.apache.ibatis.ibator.internal.util,
org.apache.ibatis.ibator.internal.util.messages,
org.apache.ibatis.ibator.logging,
org.apache.ibatis.ibator.maven,
org.apache.ibatis.ibator.plugins
Bundle-RequiredExecutionEnvironment: J2SE-1.5
=========
On 2/19/2010 9:22 AM, Jeff Butler wrote:
> Look at MANIFEST.MF in the ibator.core project. The Export-Package
> directive must list all packages in the ibator.jar file - the version
> in SVN needs an update.
>
> A small bit of OSGI loveliness. That's my best guess. I'll take a
> look at updating this in SVN later today - hopefully :)
>
> Jeff Butler
>
>
> On Fri, Feb 19, 2010 at 2:21 AM, Guy Rouillier<gu...@burntmail.com> wrote:
>> 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.<init>(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:
>>>
>>> <packageset dir="../../core/src" />
>>> to
>>> <packageset dir="../../core/ibator-core/src" />
>>>
>>> <fileset dir="../../core/htmldoc">
>>> to
>>> <fileset dir="../../core/ibator-core/doc/html">
>>>
>>> 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
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
> For additional commands, e-mail: user-java-help@ibatis.apache.org
>
>
--
Guy Rouillier
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org
Re: Ibator for ibatis 3
Posted by Jeff Butler <je...@gmail.com>.
Look at MANIFEST.MF in the ibator.core project. The Export-Package
directive must list all packages in the ibator.jar file - the version
in SVN needs an update.
A small bit of OSGI loveliness. That's my best guess. I'll take a
look at updating this in SVN later today - hopefully :)
Jeff Butler
On Fri, Feb 19, 2010 at 2:21 AM, Guy Rouillier <gu...@burntmail.com> wrote:
> 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.<init>(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:
>>
>> <packageset dir="../../core/src" />
>> to
>> <packageset dir="../../core/ibator-core/src" />
>>
>> <fileset dir="../../core/htmldoc">
>> to
>> <fileset dir="../../core/ibator-core/doc/html">
>>
>> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org
Re: Ibator for ibatis 3
Posted by Guy Rouillier <gu...@burntmail.com>.
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.<init>(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:
>
> <packageset dir="../../core/src" />
> to
> <packageset dir="../../core/ibator-core/src" />
>
> <fileset dir="../../core/htmldoc">
> to
> <fileset dir="../../core/ibator-core/doc/html">
>
> 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
Re: Ibator for ibatis 3
Posted by Guy Rouillier <gu...@burntmail.com>.
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:
<packageset dir="../../core/src" />
to
<packageset dir="../../core/ibator-core/src" />
<fileset dir="../../core/htmldoc">
to
<fileset dir="../../core/ibator-core/doc/html">
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
Re: Ibator for ibatis 3
Posted by Jeff Butler <je...@gmail.com>.
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".
Jeff Butler
On Wed, Feb 17, 2010 at 12:45 AM, Guy Rouillier <gu...@burntmail.com> wrote:
> On 11/8/2009 7:11 PM, Jeff Butler wrote:
>>
>> Ibator updates for iBATIS3 are now in SVN. I won't do a formal
>> release for a few days as I need to update the docs, but feel free to
>> check it out and play with it. Ibator is now built with Maven rather
>> than Ant, so you'll need to know how to do a Maven build. All the
>> tests pass, but there might be some situations I've not anticipated.
>> Let me know if you encounter any difficulties. The SVN link is here:
>>
>> http://svn.apache.org/repos/asf/ibatis/java/ibator/trunk/core/
>
> Jeff, iBATIS is now spreading through our company; thanks again to the whole
> development team for your hard work on such a useful platform.
>
> Any updates on a binary build of Ibator compatible with version 3 of iBATIS?
> I'm interested in the Eclipse plugin as well as core. Someone called me
> today asking about old bugs in 1.2.1 so I provided him with my local binary
> of 1.2.2, but would like to get the version 3 updates.
>
> Thanks.
>
> --
> Guy Rouillier
>
> --
> Guy Rouillier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
> For additional commands, e-mail: user-java-help@ibatis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org
Re: Ibator for ibatis 3
Posted by Guy Rouillier <gu...@burntmail.com>.
On 11/8/2009 7:11 PM, Jeff Butler wrote:
> Ibator updates for iBATIS3 are now in SVN. I won't do a formal
> release for a few days as I need to update the docs, but feel free to
> check it out and play with it. Ibator is now built with Maven rather
> than Ant, so you'll need to know how to do a Maven build. All the
> tests pass, but there might be some situations I've not anticipated.
> Let me know if you encounter any difficulties. The SVN link is here:
>
> http://svn.apache.org/repos/asf/ibatis/java/ibator/trunk/core/
Jeff, iBATIS is now spreading through our company; thanks again to the
whole development team for your hard work on such a useful platform.
Any updates on a binary build of Ibator compatible with version 3 of
iBATIS? I'm interested in the Eclipse plugin as well as core. Someone
called me today asking about old bugs in 1.2.1 so I provided him with my
local binary of 1.2.2, but would like to get the version 3 updates.
Thanks.
--
Guy Rouillier
--
Guy Rouillier
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org
Re: Ibator for ibatis 3
Posted by Jeff Butler <je...@gmail.com>.
Hi Guy,
I'm glad you are finding some value from Ibator.
I have no plans to do a generate from a select statement. I'm not
opposed to it philosophically - I just have limited time right now.
Feel free to work on a patch if you are interested.
Jeff Butler
On Thu, Nov 12, 2009 at 1:34 AM, Guy Rouillier <gu...@burntmail.com> wrote:
> Jeff Butler wrote:
>>
>> Ibator updates for iBATIS3 are now in SVN.
>
> ...
>>
>> Let me know if you encounter any difficulties.
>
> Jeff, thanks for your work on this. I've been using iBATIS 3 and Ibator
> 1.2.2 on a new project and the capabilities are great! I have one issue.
> Just yesterday, I had a complex SELECT statement I was trying to use. I
> started typing up the result map by hand and that got tedious. So, I took
> the easy way out and in the database, did a CREATE TABLE AS SELECT... ; this
> is Oracle, btw. That worked fine; I was then able to run Ibator against the
> table.
>
> My question is, with Ibator 3 will we be able to ask it to generate output
> based on a supplied SELECT statement? Or is it still restricted to tables
> (and views)? I took a quick look at the SVN repository online and the DTD
> still only shows "table" as the way to generate artifacts.
>
> Hmm, another thought. I typed up the SELECT statement in the iBATIS mapper
> file after first testing it in Oracle. I then started working on the result
> map. Would it be possible to tell Ibator to use an iBATIS SQL statement ID
> as the source for generating artifacts?
>
> Thanks.
>
> --
> Guy Rouillier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
> For additional commands, e-mail: user-java-help@ibatis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org
Re: Ibator for ibatis 3
Posted by Guy Rouillier <gu...@burntmail.com>.
Jeff Butler wrote:
> Ibator updates for iBATIS3 are now in SVN.
...
> Let me know if you encounter any difficulties.
Jeff, thanks for your work on this. I've been using iBATIS 3 and Ibator
1.2.2 on a new project and the capabilities are great! I have one
issue. Just yesterday, I had a complex SELECT statement I was trying to
use. I started typing up the result map by hand and that got tedious.
So, I took the easy way out and in the database, did a CREATE TABLE AS
SELECT... ; this is Oracle, btw. That worked fine; I was then able to
run Ibator against the table.
My question is, with Ibator 3 will we be able to ask it to generate
output based on a supplied SELECT statement? Or is it still restricted
to tables (and views)? I took a quick look at the SVN repository online
and the DTD still only shows "table" as the way to generate artifacts.
Hmm, another thought. I typed up the SELECT statement in the iBATIS
mapper file after first testing it in Oracle. I then started working on
the result map. Would it be possible to tell Ibator to use an iBATIS
SQL statement ID as the source for generating artifacts?
Thanks.
--
Guy Rouillier
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org
Re: Ibator for ibatis 3
Posted by Jeff Butler <je...@gmail.com>.
Ibator updates for iBATIS3 are now in SVN. I won't do a formal
release for a few days as I need to update the docs, but feel free to
check it out and play with it. Ibator is now built with Maven rather
than Ant, so you'll need to know how to do a Maven build. All the
tests pass, but there might be some situations I've not anticipated.
Let me know if you encounter any difficulties. The SVN link is here:
http://svn.apache.org/repos/asf/ibatis/java/ibator/trunk/core/
Jeff Butler
On Thu, Nov 5, 2009 at 11:41 PM, Zach Visagie <za...@ipay.co.za> wrote:
> On Thu, 5 Nov 2009 09:44:48 -0600
> Jeff Butler <je...@gmail.com> wrote:
>
>> Ibator for ibatis3 has been *almost* ready for some time now. I'll
>
> :)
>
>> try to get it finished and checked in to SVN this weekend.
>>
>
> Cool, thanks! In terms of our context as I described below, getting even a buggy beta version is ok for our use...
>
>
>
>> Jeff Butler
>>
>>
>> On Thu, Nov 5, 2009 at 1:17 AM, Zach Visagie <za...@ipay.co.za> wrote:
>> > Hi
>> >
>> > My comment: I have had a first look at ibatis 3 and I like it a lot. Even though annotations might not have lived up to the expected promise, we certainly have some use cases for which they are going to be very handy. Thanks for the good work guys! (I can soon retire my custom auto generated keys hack for ibatis 2)
>> >
>> > My question: We have a new project we will be working on for the next 5-7 months and I want to start using ibatis 3 and ibator. Is there any ibator code for ibatis 3 in svn that can be checked out or any binaries for a current version of ibator that supports ibatis 3?
>> >
>> > thanks
>> > Zach
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
>> > For additional commands, e-mail: user-java-help@ibatis.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
>> For additional commands, e-mail: user-java-help@ibatis.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
> For additional commands, e-mail: user-java-help@ibatis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org
Re: Ibator for ibatis 3
Posted by Zach Visagie <za...@ipay.co.za>.
On Thu, 5 Nov 2009 09:44:48 -0600
Jeff Butler <je...@gmail.com> wrote:
> Ibator for ibatis3 has been *almost* ready for some time now. I'll
:)
> try to get it finished and checked in to SVN this weekend.
>
Cool, thanks! In terms of our context as I described below, getting even a buggy beta version is ok for our use...
> Jeff Butler
>
>
> On Thu, Nov 5, 2009 at 1:17 AM, Zach Visagie <za...@ipay.co.za> wrote:
> > Hi
> >
> > My comment: I have had a first look at ibatis 3 and I like it a lot. Even though annotations might not have lived up to the expected promise, we certainly have some use cases for which they are going to be very handy. Thanks for the good work guys! (I can soon retire my custom auto generated keys hack for ibatis 2)
> >
> > My question: We have a new project we will be working on for the next 5-7 months and I want to start using ibatis 3 and ibator. Is there any ibator code for ibatis 3 in svn that can be checked out or any binaries for a current version of ibator that supports ibatis 3?
> >
> > thanks
> > Zach
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
> > For additional commands, e-mail: user-java-help@ibatis.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
> For additional commands, e-mail: user-java-help@ibatis.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org
Re: Ibator for ibatis 3
Posted by Jeff Butler <je...@gmail.com>.
Ibator for ibatis3 has been *almost* ready for some time now. I'll
try to get it finished and checked in to SVN this weekend.
Jeff Butler
On Thu, Nov 5, 2009 at 1:17 AM, Zach Visagie <za...@ipay.co.za> wrote:
> Hi
>
> My comment: I have had a first look at ibatis 3 and I like it a lot. Even though annotations might not have lived up to the expected promise, we certainly have some use cases for which they are going to be very handy. Thanks for the good work guys! (I can soon retire my custom auto generated keys hack for ibatis 2)
>
> My question: We have a new project we will be working on for the next 5-7 months and I want to start using ibatis 3 and ibator. Is there any ibator code for ibatis 3 in svn that can be checked out or any binaries for a current version of ibator that supports ibatis 3?
>
> thanks
> Zach
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
> For additional commands, e-mail: user-java-help@ibatis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org