facebook

MyEclipse 5.0M1 Oddities

  1. MyEclipse IDE
  2.  > 
  3. Installation, Configuration & Updates
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #254142 Reply

    Hi,

    First of all, let me tell you that we are so impressed with MyEclipse. It provides functionality that makes a big difference to deliver quality software. Therefore, I was very excited to try out the latest (beta) version. I didn’t know the proper mechanism for feedback, so please feel free to move this to another MyEclipse news group.

    I just downloaded Eclipse 3.2 (GA) and installed MyEclipse 5.0M1 on WindowsXP and had some odd behavior.

      I wanted to overwrite my earlier version of MyEclipse (which was working with Eclipse 3.1) and gave it the same directory (which was not the default directory under Project Files). It appeared to installed fine. When I brought up Eclipse, the “About Eclipse” menu item told me that it was running MyEclipse 4.1. We would like to continue to put the MyEclipse folder somewhere other than the default.
      After several tries, I gave up and accepted the default and Eclipse came up with the MyEclipse 5.0M1!. However, the preferencs show two versions of most items: 2 common editor prefrences followed by 2 CSS followed by 2 DTD, 1! Hibernate Config followed by 2 HTML and so on. Have you seen this before?
      When I open an existing JSP page, I get a dialog box informing me that I have “unsupported content type in editor” and I can not set any breakpoints. Moreover, when I open it in JSP Designer, it shows nothing but the dialog box. When I open it with MyEclipse “Classic” JSP editor. I still get the dialog box but end up with empty page with an error message “Unable to create this part due to an internal error. Reason for the failure: An unexpected exception was thrown” The trace is at the end of this message. The JSP page, which did open under the last version of MyEclipse, seems to only be viewed as an text file.

    Thank you and keep up the great work!
    James

    PS When should the next release (beta or GA) be expected?
    PPS Here is the trace for the errant JSP page

    
    java.lang.NullPointerException
        at com.genuitec.eclipse.webdesigner.htmleditor.HTMLMultiPageEditorPart.setActivePage(HTMLMultiPageEditorPart.java:1296)
        at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:280)
        at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:596)
        at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
        at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
        at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:290)
        at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:140)
        at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
        at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
        at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:394)
        at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1144)
        at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1097)
        at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1311)
        at org.eclipse.ui.internal.PartStack.add(PartStack.java:455)
        at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:102)
        at org.eclipse.ui.internal.PartStack.add(PartStack.java:441)
        at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:111)
        at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:60)
        at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217)
        at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207)
        at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:819)
        at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:718)
        at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:679)
        at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2586)
        at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2521)
        at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2513)
        at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2498)
        at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
        at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2493)
        at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:288)
        at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:280)
        at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:184)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
        at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
        at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
        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.invokeFramework(Main.java:336)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
        at org.eclipse.core.launcher.Main.run(Main.java:977)
        at org.eclipse.core.launcher.Main.main(Main.java:952)
    
    #254158 Reply

    Scott Anderson
    Participant

    I wanted to overwrite my earlier version of MyEclipse (which was working with Eclipse 3.1)

    Sorry you’re having a problem but I think I know what’s going on. From this comment and the issue you’re seeing, the problem appears to be that you’ve actually got both MyEclipse 4.1 and MyEclipse 5.1M1 installed in your Eclipse instance. This is a very unstable configuration and can lead to all types of odd behaviors.

    When upgrading from one major version of Eclipse and MyEclipse to the next, the best way to do that is to install a *new* Eclipse instance for use with the new MyEclipse version, then install the new MyEclipse version such that it points to the new Eclipse install. At the end of this process you would have both a working Eclipse 3.1 / MyEclipse 4.1.1 install and an Eclipse 3.2 / MyEclipse 5.0M1 install. Each of those can be installed whereever you want, but you should *not* try to install two Eclipse or MyEclipse instances in the same directory. They should remain completely isolated from each other.

    To recover this, I’d suggest you perform a new install of Eclipse 3.2 and MyEclipse 5.0M1 in new directories then open your existing workspace(s) to continue your work.

    #254183 Reply

    @support-scott wrote:

    To recover this, I’d suggest you perform a new install of Eclipse 3.2 and MyEclipse 5.0M1 in new directories then open your existing workspace(s) to continue your work.

    Yes, that did the trick. I renamed the original directories and reloaded both applications and now it runs like clockwork!

    I can’t wait for the MyEclipse 5.0M2 version. Will it be out in early July?

    Thank you again!

Viewing 3 posts - 1 through 3 (of 3 total)
Reply To: MyEclipse 5.0M1 Oddities

You must be logged in to post in the forum log in