Menu

#630 ProR Plugin No Longer Works

closed-fixed
None
5
2012-09-07
2012-07-27
Chris Hobbs
No

I have just updated my ProR plugin for Rodin and, when trying to create a new ReqIf requirements file I get the following error

java.lang.IllegalArgumentException: No ReqIf Content found. Please check errors on the console.
at org.eclipse.rmf.pror.reqif10.editor.presentation.Reqif10Editor.openReqif(Reqif10Editor.java:1090)
at org.eclipse.rmf.pror.reqif10.editor.presentation.Reqif10Editor.createPages(Reqif10Editor.java:1045)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:289)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2945)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2850)
at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2842)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2793)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2789)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2773)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2756)
at org.eclipse.rmf.pror.reqif10.editor.presentation.Reqif10ModelWizard.performFinish(Reqif10ModelWizard.java:416)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.navigator.wizards.WizardShortcutAction.run(WizardShortcutAction.java:98)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
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:344)
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:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)

This was working before I updated the plugin.

This problem was pointed out by a colleague using Rodin on a computer running Microsoft Windows; I am using Linux.

My version numbers are as follows:
Rodin Platform Version: 2.5
ProR Rodin Integration Feature 1.0.0.201206212102

I notice that there is no Category for ProR plugin but I can find no other way to report this problem.

Discussion

  • Michael Jastram

    Michael Jastram - 2012-07-28

    Chris,

    This does not seem to be a problem with the plug-in, but with the reqif-data. If you attach the file or send it to me (michael@jastram.de), I'll have a look

     
  • Michael Jastram

    Michael Jastram - 2012-07-28

    Chris,

    If your data file was fairly old before you updated, then it may be incompatible with the current version. In the very beginning, we used a non-REQIF format for a short time. If that's the problem, then I'll be happy to convert the file for you.

     
  • Laurent Voisin

    Laurent Voisin - 2012-07-30
    • assigned_to: nobody --> jastram
     
  • Chris Hobbs

    Chris Hobbs - 2012-07-30

    Hello Jastram,

    No, this was not an old reqif file, it was created about a month ago.

    I will send you a copy of the reqif for your reading pleasure.

    Thanks

    Chris

     
  • Michael Jastram

    Michael Jastram - 2012-07-30
    • status: open --> open-fixed
     
  • Michael Jastram

    Michael Jastram - 2012-07-30

    This issue has been fixed, but creates some inconvenience - at this point I'd like to apologize for this.

    Short answer: We recommend to wait for the Rodin 2.6 release and then to install ProR freshly from the preconfigured update site.

    Long answer: We just made a new service release that fixes this issue, BUT: we aligned the vesion numbers of the integration plugin with those of ProR. But this means that we're going from 1.0.0 to version 0.3.1. This in turn means that YOU CANNOT USE THE UPDATE MECHANISM to fix this.

    The easiest fix is to just wait for Rodin 2.6, due in a few days, and to install ProR through the preconfigured update site. If you want to use 2.5, you need to download a fresh installation - sorry for the inconvenience. Uninstalling ProR does not seem to work.

    In this fresh Rodin installation, DO NOT install ProR from the preconfigured update site. Instead, install it from

    http://update.formalmind.com/rodin

    That's it!

    Background: The problem materialised as, unfortunately, the update site in Rodin was mixing fixed release artefacts with nightly build artefacts.

     
  • Michael Jastram

    Michael Jastram - 2012-09-07
    • status: open-fixed --> closed-fixed
     

Log in to post a comment.

MongoDB Logo MongoDB