That isn't an error message but just a note to say that mappings in your output directory will be ignored. So it will only find mappings in other locations.
Once you've added a connection can you connect? When / if you do connect are the schema update buttons etc becoming enabled?
If not check your <workspace>/.metadata/.log file and post any Hibernator related errors here.
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have the exact same error as here above and the MetaData file contains this StackTrace:
!ENTRY org.eclipse.ui 4 0 Dec 14, 2004 16:04:25.281
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:393)
at java.util.Properties.setProperty(Properties.java:102)
at net.sf.hibernator.views.ConnectionSet.save(ConnectionSet.java:71)
at net.sf.hibernator.views.ConnectionSet.add(ConnectionSet.java:32)
at net.sf.hibernator.views.ConnectionView.add(ConnectionView.java:237)
at net.sf.hibernator.views.ConnectionView.access$1(ConnectionView.java:228)
at net.sf.hibernator.views.ConnectionView$3.run(ConnectionView.java:136)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:881)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:915)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:866)
at org.eclipse.jface.action.ActionContributionItem$7.handleEvent(ActionContributionItem.java:785)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2772)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2431)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1377)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:254)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:96)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:335)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
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:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:183)
at org.eclipse.core.launcher.Main.run(Main.java:644)
at org.eclipse.core.launcher.Main.main(Main.java:628)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just installed the hibernate plugin for eclipse. But after I added a connection, I got error message in Hibernator Log View:
Ignoring resources in Project output: /test/build
Do I have to remove or add something in Ignored Resources list?
That isn't an error message but just a note to say that mappings in your output directory will be ignored. So it will only find mappings in other locations.
Once you've added a connection can you connect? When / if you do connect are the schema update buttons etc becoming enabled?
If not check your <workspace>/.metadata/.log file and post any Hibernator related errors here.
Thanks
I have the exact same error as here above and the MetaData file contains this StackTrace:
!ENTRY org.eclipse.ui 4 0 Dec 14, 2004 16:04:25.281
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:393)
at java.util.Properties.setProperty(Properties.java:102)
at net.sf.hibernator.views.ConnectionSet.save(ConnectionSet.java:71)
at net.sf.hibernator.views.ConnectionSet.add(ConnectionSet.java:32)
at net.sf.hibernator.views.ConnectionView.add(ConnectionView.java:237)
at net.sf.hibernator.views.ConnectionView.access$1(ConnectionView.java:228)
at net.sf.hibernator.views.ConnectionView$3.run(ConnectionView.java:136)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:881)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:915)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:866)
at org.eclipse.jface.action.ActionContributionItem$7.handleEvent(ActionContributionItem.java:785)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2772)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2431)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1377)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:254)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:96)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:335)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
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:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:183)
at org.eclipse.core.launcher.Main.run(Main.java:644)
at org.eclipse.core.launcher.Main.main(Main.java:628)
I also had the very same problem. The connection does not even appear in the connection view, and i get the same exception in .log.
Same here. I'm using 3.1 and no luck. Is this bug being addressed?
I have the same error. Too bad, because Hibernator looks great....