[jbosstools-issues] [JBoss JIRA] (JBIDE-15864) Add dialog displaying errors when Plugins are added to Hybrid Mobile Project

Vlado Pakan (JIRA) jira-events at lists.jboss.org
Tue Nov 19 05:59:07 EST 2013


    [ https://issues.jboss.org/browse/JBIDE-15864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924803#comment-12924803 ] 

Vlado Pakan edited comment on JBIDE-15864 at 11/19/13 5:58 AM:
---------------------------------------------------------------

1. Create Hybrid Mobile Project
2. Open config.xml file with Cordova Configuration Editor
3. Click add plug-in
4. Add first plug-in com.blackberry.app
ERROR: No plug-in added to config.xml file but no error message displayed.
Plug-in is added top plugins directory
ERROR:
When uninstalling this plug-in via Project Explorer context menu dialog with this message is displayed: "Uninstall null (com.blackbery.app) plug-in?". There should be no null string in error message.

Error message from error log:
org.jboss.tools.aerogear.hybrid.core
{noformat}
org.eclipse.core.runtime.AssertionFailedException: assertion failed: This operation must be run within the observable's realm
	at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
	at org.eclipse.core.databinding.observable.AbstractObservable.checkRealm(AbstractObservable.java:98)
	at org.eclipse.core.databinding.observable.value.AbstractObservableValue.setValue(AbstractObservableValue.java:54)
	at org.jboss.tools.aerogear.hybrid.ui.config.internal.EssentialsPage$1.propertyChange(EssentialsPage.java:252)
	at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339)
	at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:347)
	at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:276)
	at org.jboss.tools.aerogear.hybrid.core.config.AbstractConfigObject$Property.setValue(AbstractConfigObject.java:44)
	at org.jboss.tools.aerogear.hybrid.core.config.Widget.loadItem(Widget.java:111)
	at org.jboss.tools.aerogear.hybrid.core.config.Widget.init(Widget.java:94)
	at org.jboss.tools.aerogear.hybrid.core.config.Widget.reload(Widget.java:83)
	at org.jboss.tools.aerogear.hybrid.core.config.WidgetModel.reloadEditableWidget(WidgetModel.java:187)
	at org.jboss.tools.aerogear.hybrid.core.config.WidgetModel.processPostModelEvent(WidgetModel.java:329)
	at org.eclipse.wst.sse.core.internal.model.LifecycleNotificationManager.signalLifecycleEvent(LifecycleNotificationManager.java:114)
	at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.signalLifecycleEvent(AbstractStructuredModel.java:1501)
	at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.setDirtyState(AbstractStructuredModel.java:1299)
	at org.eclipse.wst.sse.core.internal.FileBufferModelManager$FileBufferMapper.dirtyStateChanged(FileBufferModelManager.java:379)
	at org.eclipse.core.internal.filebuffers.TextFileBufferManager$3.run(TextFileBufferManager.java:706)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.filebuffers.TextFileBufferManager.fireDirtyStateChanged(TextFileBufferManager.java:704)
	at org.eclipse.core.internal.filebuffers.ResourceFileBuffer.commit(ResourceFileBuffer.java:335)
	at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.saveModel(ModelManagerImpl.java:2054)
	at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.save(AbstractStructuredModel.java:1149)
	at org.jboss.tools.aerogear.hybrid.core.config.WidgetModel.save(WidgetModel.java:196)
	at org.jboss.tools.aerogear.hybrid.core.plugin.actions.ConfigXMLUpdateAction.install(ConfigXMLUpdateAction.java:70)
	at org.jboss.tools.aerogear.hybrid.core.plugin.PluginInstallActionsRunOperation.run(PluginInstallActionsRunOperation.java:69)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2327)
	at org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.runActions(CordovaPluginManager.java:384)
	at org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.installPlugin(CordovaPluginManager.java:124)
	at org.jboss.tools.aerogear.hybrid.ui.plugins.internal.CordovaPluginWizard$PluginInstallOperation.execute(CordovaPluginWizard.java:123)
	at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
	at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
{noformat}

Not sure if this is part of this issue or new issue should be created for it.
                
      was (Author: vpakan):
    1. Create Hybrid Mobile Project
2. Open config.xml file with Cordova Configuration Editor
3. Click add plug-in
4. Add first plug-in com.blackberry.app
ERROR: No plug-in added to config.xml file but no error message displayed.
Plug-in is added top plugins directory

Not sure if this is part of this issue or new issue should be created for it.
                  
> Add dialog displaying errors when Plugins are added to Hybrid Mobile Project
> ----------------------------------------------------------------------------
>
>                 Key: JBIDE-15864
>                 URL: https://issues.jboss.org/browse/JBIDE-15864
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: aerogear-hybrid
>    Affects Versions: 4.1.1.Beta1
>            Reporter: Vlado Pakan
>            Assignee: Gorkem Ercan
>             Fix For: 4.1.1.CR1
>
>
> Sometimes when adding Plugins to Hybrid Mobile project via Cordova Configuration Editor some errors are happening and added Plugins are different than Plugins selected to be added. This is very confusing for user. Would be nice to have some dialog explaining errors which happened while adding Plugins so user know what has happened

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list