- This topic has 52 replies, 12 voices, and was last updated 17 years, 2 months ago by Riyad Kalla.
-
AuthorPosts
-
pppooleMemberPiet’s solution doesn’t work for me as I am not using any of the caps that use the commons-beanutils libraries. My errors seem to stem from the cglib libraries. Here are the libraries I am using:
JRE System Library (jre1.6.0)
Java EE 5 Libraries
Spring 2.0 Core Libraries
Spring 2.0 Persistence Core Libraries
Spring 2.0 AOP Libraries
Hibernate 3.2 Core Libraries
Hibernate 3.2 Annotations & Entity ManagerI am using MyEclipse 6.0GA (bundled with Eclipse 3.3).
Please let me know if there are any more details you would need.
Does anyone else have a workaround in the meantime?
gcstang — did you include all the libraries for both packages (hibernate and spring) when creating your user libs or did you take the time to break up the libs do remove duplicates (if there are any) and libraries that you don’t need?
Thanks.
pppooleMemberProblem solved. For those of you using Spring and Hibernate (and probably any other capability using cglib-nodep-2.1_3), try the following:
1. download the spring libraries to get cglib-nodep-2.1_3.jar (there maybe other, easier sources)
2. goto Window–>Preferences–>MyEclipse–>Project Capabilities–>Spring
3. on the right side, select the Spring 2 tab and in the drop down select Spring 2.0 AOP Libraries
4. remove the cglib-nodep-2.1_3
5. add the new cglib-nodep-2.1_3 that you got from Spring.I believe that you could also unzip the jar provided in your MyEclipse, remove the signature stuff from the META-INF directory, and re-jar it. However, I have not tested this…
Final note… You may have to do this same procedure with Commons-BeanUtils per Piet’s earlier post if you are using any of the capabilities that use that library.
Good luck!
Riyad KallaMemberGuys we are getting this fixed very shortly, please don’t go trashing the JARs inside the plugin dirs in your MyEclipse install. Either adjust the settings under the Project Capabilities preferences for now, or creating custom User Libraries and adding them to your build path will do the trick.
Again, we are sorry for this PIA.
gcstangMember@pppoole wrote:
Piet’s solution doesn’t work for me as I am not using any of the caps that use the commons-beanutils libraries. My errors seem to stem from the cglib libraries. Here are the libraries I am using:
JRE System Library (jre1.6.0)
Java EE 5 Libraries
Spring 2.0 Core Libraries
Spring 2.0 Persistence Core Libraries
Spring 2.0 AOP Libraries
Hibernate 3.2 Core Libraries
Hibernate 3.2 Annotations & Entity ManagerI am using MyEclipse 6.0GA (bundled with Eclipse 3.3).
Please let me know if there are any more details you would need.
Does anyone else have a workaround in the meantime?
gcstang — did you include all the libraries for both packages (hibernate and spring) when creating your user libs or did you take the time to break up the libs do remove duplicates (if there are any) and libraries that you don’t need?
Thanks.
What I ended up doing in the end was just using the Hibernate 3.1 MyEclipse Libs and downloading the Spring jars and adding those to my project. I attempted to create the UserLib with Spring 1.2.9 but kept having issues with some jars not being put on the classpath or available so I ended up adding them all to my project and that worked wonderfully for now. I’ll keep it this way until the issues are resolved.
Riyad KallaMemberGuys, were you able to get the Hotfix from the update site this morning? You can use MyEclipse > Add Features… if you haven’t seen it yet to install it.
We’d like to know if everything is fixed now.
pppooleMemberYup. Did the trick for me.
Thank you!
denmillsMemberIt worked for me,
Thanks for the quick turnaround on this
gcstangMemberI tried this again and it won’t work with Hibernate 3.1 and Spring 1.2.9 I get java.lang.NoClassDefFoundError: org/hibernate/cfg/HbmBinder$SecondPass but if I change to Hibernate 3.0 it works.
However I keep randomly getting an error box popup in Eclipse that say’s Multiple Errors have Occurred.
“Multiple operations have reported errors. Select an error to view its details”
If I click on Details >> then all I see is Error in a text area box.
If I look into the workspace .log file I see SWT errors.Looks like:
!ENTRY org.eclipse.ui 4 0 2007-08-28 06:59:33.515
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: Argument cannot be null)
at org.eclipse.swt.SWT.error(SWT.java:3563)
at org.eclipse.swt.SWT.error(SWT.java:3481)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:126)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
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:504)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
Caused by: java.lang.IllegalArgumentException: Argument cannot be null
at org.eclipse.swt.SWT.error(SWT.java:3547)
at org.eclipse.swt.SWT.error(SWT.java:3481)
at org.eclipse.swt.SWT.error(SWT.java:3452)
at org.eclipse.swt.widgets.Widget.error(Widget.java:432)
at org.eclipse.swt.widgets.Link.setText(Link.java:571)
at org.eclipse.ui.internal.progress.ProgressInfoItem.updateText(ProgressInfoItem.java:773)
at org.eclipse.ui.internal.progress.ProgressInfoItem.setLinkText(ProgressInfoItem.java:759)
at org.eclipse.ui.internal.progress.ProgressInfoItem.refresh(ProgressInfoItem.java:530)
at org.eclipse.ui.internal.progress.ProgressInfoItem.setDisplayed(ProgressInfoItem.java:902)
at org.eclipse.ui.internal.progress.ProgressInfoItem.setDisplayed(ProgressInfoItem.java:888)
at org.eclipse.ui.internal.progress.DetailedProgressViewer.updateVisibleItems(DetailedProgressViewer.java:503)
at org.eclipse.ui.internal.progress.DetailedProgressViewer.access$0(DetailedProgressViewer.java:497)
at org.eclipse.ui.internal.progress.DetailedProgressViewer$2.controlMoved(DetailedProgressViewer.java:99)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:210)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:943)
at org.eclipse.swt.widgets.Control.WM_MOVE(Control.java:4186)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3718)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4351)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2259)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4351)
at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method)
at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1235)
at org.eclipse.swt.widgets.Control.setBounds(Control.java:2521)
at org.eclipse.swt.widgets.Control.setBounds(Control.java:2503)
at org.eclipse.swt.widgets.Control.setLocation(Control.java:2829)
at org.eclipse.swt.custom.ScrolledComposite.setContent(ScrolledComposite.java:438)
at org.eclipse.ui.internal.progress.DetailedProgressViewer.updateForShowingProgress(DetailedProgressViewer.java:180)
at org.eclipse.ui.internal.progress.DetailedProgressViewer.remove(DetailedProgressViewer.java:424)
at org.eclipse.ui.internal.progress.ProgressViewerContentProvider.remove(ProgressViewerContentProvider.java:218)
at org.eclipse.ui.internal.progress.ProgressViewUpdater$1.runInUIThread(ProgressViewUpdater.java:280)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
… 23 more
gcstangMember@gcstang wrote:
I tried this again and it won’t work with Hibernate 3.1 and Spring 1.2.9 I get java.lang.NoClassDefFoundError: org/hibernate/cfg/HbmBinder$SecondPass but if I change to Hibernate 3.0 it works.
However I keep randomly getting an error box popup in Eclipse that say’s Multiple Errors have Occurred.
“Multiple operations have reported errors. Select an error to view its details”
If I click on Details >> then all I see is Error in a text area box.
If I look into the workspace .log file I see SWT errors.Looks like:
!ENTRY org.eclipse.ui 4 0 2007-08-28 06:59:33.515
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: Argument cannot be null)
at org.eclipse.swt.SWT.error(SWT.java:3563)
at org.eclipse.swt.SWT.error(SWT.java:3481)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:126)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
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:504)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
Caused by: java.lang.IllegalArgumentException: Argument cannot be null
at org.eclipse.swt.SWT.error(SWT.java:3547)
at org.eclipse.swt.SWT.error(SWT.java:3481)
at org.eclipse.swt.SWT.error(SWT.java:3452)
at org.eclipse.swt.widgets.Widget.error(Widget.java:432)
at org.eclipse.swt.widgets.Link.setText(Link.java:571)
at org.eclipse.ui.internal.progress.ProgressInfoItem.updateText(ProgressInfoItem.java:773)
at org.eclipse.ui.internal.progress.ProgressInfoItem.setLinkText(ProgressInfoItem.java:759)
at org.eclipse.ui.internal.progress.ProgressInfoItem.refresh(ProgressInfoItem.java:530)
at org.eclipse.ui.internal.progress.ProgressInfoItem.setDisplayed(ProgressInfoItem.java:902)
at org.eclipse.ui.internal.progress.ProgressInfoItem.setDisplayed(ProgressInfoItem.java:888)
at org.eclipse.ui.internal.progress.DetailedProgressViewer.updateVisibleItems(DetailedProgressViewer.java:503)
at org.eclipse.ui.internal.progress.DetailedProgressViewer.access$0(DetailedProgressViewer.java:497)
at org.eclipse.ui.internal.progress.DetailedProgressViewer$2.controlMoved(DetailedProgressViewer.java:99)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:210)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:943)
at org.eclipse.swt.widgets.Control.WM_MOVE(Control.java:4186)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3718)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4351)
at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2259)
at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4351)
at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method)
at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1235)
at org.eclipse.swt.widgets.Control.setBounds(Control.java:2521)
at org.eclipse.swt.widgets.Control.setBounds(Control.java:2503)
at org.eclipse.swt.widgets.Control.setLocation(Control.java:2829)
at org.eclipse.swt.custom.ScrolledComposite.setContent(ScrolledComposite.java:438)
at org.eclipse.ui.internal.progress.DetailedProgressViewer.updateForShowingProgress(DetailedProgressViewer.java:180)
at org.eclipse.ui.internal.progress.DetailedProgressViewer.remove(DetailedProgressViewer.java:424)
at org.eclipse.ui.internal.progress.ProgressViewerContentProvider.remove(ProgressViewerContentProvider.java:218)
at org.eclipse.ui.internal.progress.ProgressViewUpdater$1.runInUIThread(ProgressViewUpdater.java:280)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
… 23 moreI meant to say whatever Spring 1.2 is in the MyEclipse Lib.
Riyad KallaMemberGuys,
thanks for letting us know it did the trick. I’ll tell the dev team.gcstang that’s a different problem than the JAR Signer problem. Did you by chance edit any of your project capabilities libraries? You can go back and Restore Defaults on all of them and restart using -clean to make sure MyEclipse throws out all the old references and uses it’s own libs to see if that fixes it.
gcstangMemberOk I did the clean now I get the same type of popup with an actual error:
Initializing Java Tooling
Reason : assertion failed : Path for IClasspathEntry must be absolute
Riyad KallaMembergcstang,
This is sounding a lot like an installation problem. ICLasspathENtry is from the platform, you normally shouldn’t be getting core platform errors like that.I would suggest downloading the MyEclipse 6.0 GA All in One installer, the running it and make sure that you install it to a brand new directory that doesn’t exist. After the install is done, fire it up and reopen your existing workspace.
gcstangMemberThe all in one is the installer I used, should I download and install it again?
Riyad KallaMemberJust to make sure, I would. Please make sure that:
* You install to a brand new directory that you know doesn’t exist.
* When asked for the Start Menu group name, try and name it something else to make sure that it creates a new group of shortcuts for you and doesn’t get confused with an existing install.
* When you go to load your workspace up for the first time, edit the shortcut used to start MyEclipse and add “-clean” right before the “-vm” argument and then run it, and open your existing workspace.
Steve PriorMemberI notice the hotfix isn’t yet available for download from the download page. This means those of us who install MyEclipse in a network not connected to the Internet are currently out of luck for the fix. Will you shortly be adding it at least to the archived discovery site or doing a dot release of MyEclipse?
-
AuthorPosts