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<guyr-...@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-unsubscr...@ibatis.apache.org
For additional commands, e-mail: user-java-h...@ibatis.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org
For additional commands, e-mail: user-java-h...@ibatis.apache.org
--
Guy Rouillier
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org
For additional commands, e-mail: user-java-h...@ibatis.apache.org
