[JBoss JIRA] (JBIDE-21203) two different incompatible versions of org.eclipse.mylyn.context_feature in JBT/JBDS vs Central TPs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21203?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21203:
-------------------------------
Summary: two different incompatible versions of org.eclipse.mylyn.context_feature in JBT/JBDS vs Central TPs (was: two differen versions of org.eclipse.mylyn.context_feature in JBT/JBDS vs Central TPs)
> two different incompatible versions of org.eclipse.mylyn.context_feature in JBT/JBDS vs Central TPs
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21203
> URL: https://issues.jboss.org/browse/JBIDE-21203
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> {code}
> [p2.dir] Cannot complete the install because one or more required items could not be found.
> [p2.dir] Software being installed: Mylyn Context Connector: Java Development 3.17.0.v20150828-2014 (org.eclipse.mylyn.java_feature.feature.group 3.17.0.v20150828-2014)
> [p2.dir] Missing requirement: Mylyn Task-Focused Interface 3.17.0.v20150625-2044 (org.eclipse.mylyn.context_feature.feature.group 3.17.0.v20150625-2044) requires 'org.eclipse.mylyn_feature.feature.group [3.17.0,3.18.0)' but it could not be found
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: Mylyn Context Connector: Java Development 3.17.0.v20150828-2014 (org.eclipse.mylyn.java_feature.feature.group 3.17.0.v20150828-2014)
> [p2.dir] To: org.eclipse.mylyn.context_feature.feature.group [3.17.0,3.18.0)
> [p2.dir] Application failed, log file location: /mnt/hudson_workspace/workspace/jbosstools-composite-install_master/eclipse/configuration/1449545575243.log
> [p2.dir]
> [p2.dir] !ENTRY org.eclipse.equinox.p2.director 4 10053 2015-12-07 22:34:28.175
> [p2.dir] !MESSAGE Cannot complete the install because one or more required items could not be found.
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2015-12-07 22:34:28.175
> [p2.dir] !MESSAGE Software being installed: Mylyn Context Connector: Java Development 3.17.0.v20150828-2014 (org.eclipse.mylyn.java_feature.feature.group 3.17.0.v20150828-2014)
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2015-12-07 22:34:28.175
> [p2.dir] !MESSAGE Missing requirement: Mylyn Task-Focused Interface 3.17.0.v20150625-2044 (org.eclipse.mylyn.context_feature.feature.group 3.17.0.v20150625-2044) requires 'org.eclipse.mylyn_feature.feature.group [3.17.0,3.18.0)' but it could not be found
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2015-12-07 22:34:28.175
> [p2.dir] !MESSAGE Cannot satisfy dependency:
> [p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-12-07 22:34:28.175
> [p2.dir] !MESSAGE From: Mylyn Context Connector: Java Development 3.17.0.v20150828-2014 (org.eclipse.mylyn.java_feature.feature.group 3.17.0.v20150828-2014)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21203) two differen versions of org.eclipse.mylyn.context_feature in JBT/JBDS vs Central TPs
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21203:
----------------------------------
Summary: two differen versions of org.eclipse.mylyn.context_feature in JBT/JBDS vs Central TPs
Key: JBIDE-21203
URL: https://issues.jboss.org/browse/JBIDE-21203
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: central, target-platform
Affects Versions: 4.4.0.Alpha1
Reporter: Nick Boldt
{code}
[p2.dir] Cannot complete the install because one or more required items could not be found.
[p2.dir] Software being installed: Mylyn Context Connector: Java Development 3.17.0.v20150828-2014 (org.eclipse.mylyn.java_feature.feature.group 3.17.0.v20150828-2014)
[p2.dir] Missing requirement: Mylyn Task-Focused Interface 3.17.0.v20150625-2044 (org.eclipse.mylyn.context_feature.feature.group 3.17.0.v20150625-2044) requires 'org.eclipse.mylyn_feature.feature.group [3.17.0,3.18.0)' but it could not be found
[p2.dir] Cannot satisfy dependency:
[p2.dir] From: Mylyn Context Connector: Java Development 3.17.0.v20150828-2014 (org.eclipse.mylyn.java_feature.feature.group 3.17.0.v20150828-2014)
[p2.dir] To: org.eclipse.mylyn.context_feature.feature.group [3.17.0,3.18.0)
[p2.dir] Application failed, log file location: /mnt/hudson_workspace/workspace/jbosstools-composite-install_master/eclipse/configuration/1449545575243.log
[p2.dir]
[p2.dir] !ENTRY org.eclipse.equinox.p2.director 4 10053 2015-12-07 22:34:28.175
[p2.dir] !MESSAGE Cannot complete the install because one or more required items could not be found.
[p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2015-12-07 22:34:28.175
[p2.dir] !MESSAGE Software being installed: Mylyn Context Connector: Java Development 3.17.0.v20150828-2014 (org.eclipse.mylyn.java_feature.feature.group 3.17.0.v20150828-2014)
[p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2015-12-07 22:34:28.175
[p2.dir] !MESSAGE Missing requirement: Mylyn Task-Focused Interface 3.17.0.v20150625-2044 (org.eclipse.mylyn.context_feature.feature.group 3.17.0.v20150625-2044) requires 'org.eclipse.mylyn_feature.feature.group [3.17.0,3.18.0)' but it could not be found
[p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2015-12-07 22:34:28.175
[p2.dir] !MESSAGE Cannot satisfy dependency:
[p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-12-07 22:34:28.175
[p2.dir] !MESSAGE From: Mylyn Context Connector: Java Development 3.17.0.v20150828-2014 (org.eclipse.mylyn.java_feature.feature.group 3.17.0.v20150828-2014)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21145) Composite install job does not reliably install all JBT IUs and so does not see changes between CI builds
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21145:
------------------------------------
Max, you're giving me whiplash here. First you agree that since composite install test is a DIFFERENT installation test than the aggregate one, it makes sense to keep it:
"It still makes sense to have composite install tests running since not everyting is in sync for aggregateand the composite"
Then you state it's not necessary based on an incorrect assumption: that they're doing the same thing. Let me repeat. Again. The composite install test is NOT the same as the aggregate install tests.
"I see both me and mistria repeating that the composite install test is unnecessary assuming it does the same as building the aggregate"
As to what all this has to do w/ JBDS, please re-read what I said. We do MANY install tests while building JBT and JBDS. Most are done once everything is built and published to CI, since the install tests require that all the moving pieces stop moving for a little bit. The composite install test is the only one that tests composition of the aggregate BEFORE it's built. So, it's a valuable test.
If you disagree, you can simply ignore it and let the aggregate jobs run on a schedule, checking for github changes (which they do), or on a schedule rebuilding and then checking buildinfo.json or p2diff to see if a publish is worthwhile (which they do).
If you want more frequent github (Jenkins built-in) or sha/p2diff checks (JBIDE-16970), we can certainly make that change.
"We could directly run the aggregator every 3 hours."
I'm good with that idea, if there's a need for it. Do we need to rebuild the aggregate every 3 hrs just to see if there's new bits to publish?
As to the value of the composite install test... well, I just proved another case where it's useful. Yesterday I added the Central/EA URLs into the mix of sites from which the install is being done, in order to resolve JBIDE-21189. In 4.3.mars branch, the composite install is now blue/yellow again, instead of failing with:
{code}
[p2.dir] From: JBoss Tools Java Standard Tools Tests Developer Resources 3.7.1.Beta1-v201 [p2.dir] Missing requirement: Tests Plug-in 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.angularjs.test 3.7.1.Beta1-v20151204-1915-B61) requires 'bundle org.eclipse.angularjs.core 1.1.0' but it could not be found
51204-1915-B61 (org.jboss.tools.jst.test.feature.source.feature.group 3.7.1.Beta1-v20151204-1915-B61)
{code}
But in master branch, I'm getting a new problem -- there are two different versions of org.eclipse.mylyn.context_feature - 3.17.0.v20150625-2044 and 3.18.0.v20151014-2324 - in our target platforms. So, once again, the composite install job finds another problem! [^jbide21145-conflict-between-tp-and-central.png]
So, *please* can we stop bitching about its value? We do this every year, but haven't managed to to find (or build) a BETTER way to find build/install problems like this, or to orchestrate parallel build jobs (core aggregate, coretests aggregate).
> Composite install job does not reliably install all JBT IUs and so does not see changes between CI builds
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21145
> URL: https://issues.jboss.org/browse/JBIDE-21145
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
> Attachments: jbide21145-conflict-between-tp-and-central.png
>
>
> We have often seen old artifacts on nightly sites (mars and neon too).
> It seems that the composite-install job [0], [1] is not reliable. So, the downstream JBT aggregate builds [2], [3] are not triggered automatically to pick up all new changes in the upstream JBT component site builds.
> [0] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-...
> [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-...
> [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... (latest build shows: "Nov 27, 2015 6:15 AM NOT PUBLISHED: UNCHANGED")
> [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... (latest build shows: "Nov 27, 2015 3:43 AM NOT PUBLISHED: UNCHANGED")
> Please investigate.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21202) Central is stuck on "Loading JBoss Central" when offline
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21202?page=com.atlassian.jira.plugi... ]
Radim Hopp updated JBIDE-21202:
-------------------------------
Fix Version/s: 4.3.1.Beta1
> Central is stuck on "Loading JBoss Central" when offline
> --------------------------------------------------------
>
> Key: JBIDE-21202
> URL: https://issues.jboss.org/browse/JBIDE-21202
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.1.Beta1
> Environment: JBDS 9.1.0.Beta1-v20151208-1226-B169
> Reporter: Radim Hopp
> Priority: Blocker
> Fix For: 4.3.1.Beta1
>
>
> When started without internet access, Central is stuck on "Loading JBoss Central, please wait..." and error pops up:
> {noformat}
> Unable to open /resources/jbosstools-central-webpage.zip
> Can't find embedded central zip
> {noformat}
> even though studio/plugins/org.jboss.tools.central_2.0.1.Beta1-v20151116-2016-B57/resources/jbosstools-central-webpage.zip is present on file system.
> In JBDS 9.0.0.GA Central can be loaded without issues when offline.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21202) Central is stuck on "Loading JBoss Central" when offline
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21202?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-21202:
------------------------------------
This only happens with fresh workspace. Trying it with workspace, where central has been loaded at least once, everything is ok.
> Central is stuck on "Loading JBoss Central" when offline
> --------------------------------------------------------
>
> Key: JBIDE-21202
> URL: https://issues.jboss.org/browse/JBIDE-21202
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.1.Beta1
> Environment: JBDS 9.1.0.Beta1-v20151208-1226-B169
> Reporter: Radim Hopp
> Priority: Blocker
>
> When started without internet access, Central is stuck on "Loading JBoss Central, please wait..." and error pops up:
> {noformat}
> Unable to open /resources/jbosstools-central-webpage.zip
> Can't find embedded central zip
> {noformat}
> even though studio/plugins/org.jboss.tools.central_2.0.1.Beta1-v20151116-2016-B57/resources/jbosstools-central-webpage.zip is present on file system.
> In JBDS 9.0.0.GA Central can be loaded without issues when offline.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21201) TernError: No type found at the given position.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21201?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21201:
-----------------------------------
Component/s: upstream
> TernError: No type found at the given position.
> -----------------------------------------------
>
> Key: JBIDE-21201
> URL: https://issues.jboss.org/browse/JBIDE-21201
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, upstream
> Affects Versions: 4.3.0.Beta1
> Environment: tern 1.1.0
> Reporter: Pavol Srna
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> 1. Create JSF 1.2 Kick Start project
> 2. Open inputUserName.jsp in VPE
> 3. Click on 'user' text within <h:inputText> tag
> 4. Press F3 key
> {code}
> tern.TernException: TernError: No type found at the given position.
> at tern.server.DefaultResponseHandler.getData(DefaultResponseHandler.java:45)
> at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:43)
> at tern.eclipse.ide.internal.core.resources.IDETernServerAsyncReqProcessor.run(IDETernServerAsyncReqProcessor.java:104)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: tern.TernException: TernError: No type found at the given position.
> at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:86)
> at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:163)
> at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127)
> at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:42)
> ... 2 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21201) TernError: No type found at the given position.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21201?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21201:
--------------------------------------
Assignee: Victor Rubezhny
> TernError: No type found at the given position.
> -----------------------------------------------
>
> Key: JBIDE-21201
> URL: https://issues.jboss.org/browse/JBIDE-21201
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, upstream
> Affects Versions: 4.3.0.Beta1
> Environment: tern 1.1.0
> Reporter: Pavol Srna
> Assignee: Victor Rubezhny
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> 1. Create JSF 1.2 Kick Start project
> 2. Open inputUserName.jsp in VPE
> 3. Click on 'user' text within <h:inputText> tag
> 4. Press F3 key
> {code}
> tern.TernException: TernError: No type found at the given position.
> at tern.server.DefaultResponseHandler.getData(DefaultResponseHandler.java:45)
> at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:43)
> at tern.eclipse.ide.internal.core.resources.IDETernServerAsyncReqProcessor.run(IDETernServerAsyncReqProcessor.java:104)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: tern.TernException: TernError: No type found at the given position.
> at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:86)
> at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:163)
> at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127)
> at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:42)
> ... 2 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21201) TernError: No type found at the given position.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21201?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21201:
----------------------------------------
Is this something new or we had this issue in previous tern?
> TernError: No type found at the given position.
> -----------------------------------------------
>
> Key: JBIDE-21201
> URL: https://issues.jboss.org/browse/JBIDE-21201
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, upstream
> Affects Versions: 4.3.0.Beta1
> Environment: tern 1.1.0
> Reporter: Pavol Srna
> Assignee: Victor Rubezhny
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> 1. Create JSF 1.2 Kick Start project
> 2. Open inputUserName.jsp in VPE
> 3. Click on 'user' text within <h:inputText> tag
> 4. Press F3 key
> {code}
> tern.TernException: TernError: No type found at the given position.
> at tern.server.DefaultResponseHandler.getData(DefaultResponseHandler.java:45)
> at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:43)
> at tern.eclipse.ide.internal.core.resources.IDETernServerAsyncReqProcessor.run(IDETernServerAsyncReqProcessor.java:104)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: tern.TernException: TernError: No type found at the given position.
> at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:86)
> at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:163)
> at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127)
> at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:42)
> ... 2 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21200) Plug-in "org.jboss.tools.vpe" was unable to instantiate class "org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21200?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21200:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
> Plug-in "org.jboss.tools.vpe" was unable to instantiate class "org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21200
> URL: https://issues.jboss.org/browse/JBIDE-21200
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.3.0.Beta1
> Environment: Mac OS
> Reporter: Pavol Srna
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Beta1, 4.4.0.Alpha1
>
>
> 1. Create JSF 1.2 Kick Start project
> 2. Open inputUserName.jsp in VPE
> 3. Right Click on 'user' text within <h:inputText> tag
> {code}
> org.eclipse.core.runtime.CoreException: Plug-in "org.jboss.tools.vpe" was unable to instantiate class "org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem".
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:186)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.ui.internal.util.Util.safeLoadExecutableExtension(Util.java:872)
> at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.createContributionItem(DynamicMenuContributionItem.java:234)
> at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.getContributionItem(DynamicMenuContributionItem.java:227)
> at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.fill(DynamicMenuContributionItem.java:206)
> at org.eclipse.jface.action.MenuManager.doItemFill(MenuManager.java:724)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:806)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:665)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.scheduleManagerUpdate(MenuManagerRenderer.java:1164)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.processContents(MenuManagerRenderer.java:636)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.subscribeTopicChildAdded(MenuManagerRenderer.java:313)
> at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler$1.run(UIEventObjectSupplier.java:56)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4781)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211)
> at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler.handleEvent(UIEventObjectSupplier.java:53)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:85)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.emf.ecore.util.EcoreEList.dispatchNotification(EcoreEList.java:249)
> at org.eclipse.emf.common.notify.impl.NotifyingListImpl.addUnique(NotifyingListImpl.java:356)
> at org.eclipse.emf.common.util.AbstractEList.add(AbstractEList.java:341)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.mergeIntoModel(ContributionRecord.java:250)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.processAddition(MenuManagerRenderer.java:554)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.generateContributions(MenuManagerRenderer.java:529)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.processContributions(MenuManagerRenderer.java:494)
> at org.eclipse.ui.internal.PopupMenuExtender.addMenuContributions(PopupMenuExtender.java:409)
> at org.eclipse.ui.internal.PopupMenuExtender.menuAboutToShow(PopupMenuExtender.java:381)
> at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:333)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:466)
> at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:461)
> at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:493)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1495)
> at org.eclipse.swt.widgets.Menu.menuWillOpen(Menu.java:811)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5746)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSMenu.popUpContextMenu(NSMenu.java:77)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:280)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:4149)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3691)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem.<init>(SetupTemplateContributionItem.java:55)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at java.lang.Class.newInstance(Class.java:442)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
> ... 81 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months