[JBoss JIRA] (JBDS-4258) Could not resolve modules m2e and testng
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4258?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4258:
----------------------------------
remove testng and m2e from devstudio rpm; depend on testng and m2e rpm packages instead
> Could not resolve modules m2e and testng
> ----------------------------------------
>
> Key: JBDS-4258
> URL: https://issues.jboss.org/browse/JBDS-4258
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.3.0.AM2
> Environment: RHEL7, HRSCL 2.4. Alpha 1.0
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.3.0.GA
>
> Attachments: rh-eclipse46-devstudio10.3.log.with_RHSCL_2.4.alfa_1.0.20170126-0712.txt
>
>
> Devstudio installed upon rh-eclipse46-base from HRSCL 2.4. Alpha 1.0 (1) fails to start because of bundle conflict.
> Base from HRSCL 2.4. newly contains m2e and testng which are also contained in Devstudio. So we probably need to remove m2e and testng from Devstudio.
> (1) http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.4-RHEL-7-Alpha...
> Log: [^rh-eclipse46-devstudio10.3.log.with_RHSCL_2.4.alfa_1.0.20170126-0712.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23422:
------------------------------------------
[~rcernich] thx for the pointers, looking what I can do here.
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.4.3.Final
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Rob Cernich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Rob Cernich commented on JBIDE-23422:
-------------------------------------
Also, don't forget to cancel the timer when you close the connection.
Simply put, I send a SPDY ping message every 30s or so. I can't remember if I added anything to check if data had been sent to prevent sending a ping if it wasn't needed.
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.4.3.Final
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23814) Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23814?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23814:
-------------------------------------
Fix Version/s: 4.4.3.Final
> Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error
> -----------------------------------------------------------------
>
> Key: JBIDE-23814
> URL: https://issues.jboss.org/browse/JBIDE-23814
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: Red Hat JBoss Developer Studio
> Version: 10.2.0.GA
> Build id: GA-v20161125-1418-B55
> Build date: 20161125-1418
> JBoss Openshift UI Plugin
> Version: 3.3.1.v20161125-0956
> OpenShift
> openshift v3.3.1.3
> Reporter: Siamak Sadeghianfar
> Priority: Critical
> Fix For: 4.4.3.Final
>
>
> When adding a Server Adapter for an JBoss EAP 7 based deployments on OpenShift, operation fails with this error:
> {{Could not sync /private/tmp/workspace-demo/.metadata/.plugins/org.jboss.ide.eclipse.as.core/inventory-dev-ssadeghi@inventory/deploy to all pods running the service inventory
> OpenShiftBinaryCapability process exited: error: auth info "ssadeghi-redhat.com" does not exist}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23814) Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23814?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23814:
-------------------------------------
Priority: Critical (was: Major)
> Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error
> -----------------------------------------------------------------
>
> Key: JBIDE-23814
> URL: https://issues.jboss.org/browse/JBIDE-23814
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: Red Hat JBoss Developer Studio
> Version: 10.2.0.GA
> Build id: GA-v20161125-1418-B55
> Build date: 20161125-1418
> JBoss Openshift UI Plugin
> Version: 3.3.1.v20161125-0956
> OpenShift
> openshift v3.3.1.3
> Reporter: Siamak Sadeghianfar
> Priority: Critical
> Fix For: 4.4.3.Final
>
>
> When adding a Server Adapter for an JBoss EAP 7 based deployments on OpenShift, operation fails with this error:
> {{Could not sync /private/tmp/workspace-demo/.metadata/.plugins/org.jboss.ide.eclipse.as.core/inventory-dev-ssadeghi@inventory/deploy to all pods running the service inventory
> OpenShiftBinaryCapability process exited: error: auth info "ssadeghi-redhat.com" does not exist}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23767) Jenkins build for OpenShift is failing with mirror problems
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23767?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23767:
------------------------------------------
[~nickboldt] ok, cool. thx!
> Jenkins build for OpenShift is failing with mirror problems
> -----------------------------------------------------------
>
> Key: JBIDE-23767
> URL: https://issues.jboss.org/browse/JBIDE-23767
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: build
> Fix For: 4.4.3.AM2
>
>
> Starting with [#1782|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Master/job/jbosstools-openshift_master/1782/] jenkins build for OpenShift started to fail with problems in the mirror tool (basic maven build competes successfully):
> {code}
> Results :
> Tests run: 15, Failures: 0, Errors: 0, Skipped: 0
> [INFO] All tests passed!
> [INFO]
> [INFO] --- tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) @ org.jboss.tools.openshift.cdk.server.test ---
> [INFO] Skipped
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] openshift.tests .................................... SUCCESS [ 1.115 s]
> [INFO] org.jboss.tools.openshift.egit.test ................ SUCCESS [ 20.698 s]
> [INFO] org.jboss.tools.openshift.express.test ............. SUCCESS [ 17.420 s]
> [INFO] org.jboss.tools.openshift.test ..................... SUCCESS [ 40.148 s]
> [INFO] org.jboss.tools.openshift.cdk.server.test .......... SUCCESS [ 17.296 s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 02:20 min
> [INFO] Finished at: 2017-01-18T05:49:08-05:00
> [INFO] Final Memory: 68M/657M
> [INFO] ------------------------------------------------------------------------
> Terminating xvnc.
> $ vncserver -kill :91
> Killing Xvnc process ID 589
> Checking console output
> /qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-openshift_master/builds/1788/log:
> [WARNING] Mirror tool: Problems resolving provisioning plan.: [Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.js.feature.source.feature.group [1.0.0.v20161116-1518].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.js.feature.feature.group [1.0.0.v20161116-1518].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.test.feature.source.feature.group [3.3.1.v20161124-1528].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.cdk.test.feature.feature.group [3.3.1.v20160928-2042].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.feature.feature.group [3.3.1.v20161202-0851].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.express.test.feature.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.egit.integration.feature.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.egit.integration.test.feature.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.feature.source.feature.group [3.3.1.v20161202-0851].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.egit.integration.feature.source.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.test.feature.feature.group [3.3.1.v20161124-1528].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.express.feature.source.feature.group [3.3.1.v20161117-0751].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.cdk.feature.feature.group [3.3.1.v20161025-0131].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.egit.integration.test.feature.source.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.cdk.test.feature.source.feature.group [3.3.1.v20160928-2042].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.express.test.feature.source.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.express.feature.feature.group [3.3.1.v20161117-0751].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.cdk.feature.source.feature.group [3.3.1.v20161025-0131].]
> Build step 'Jenkins Text Finder' changed build result to FAILURE
> Archiving artifacts
> Recording test results
> [description-setter] Description set:
> Sending e-mails to: jbosstools-builds(a)lists.jboss.org adietish(a)redhat.com jcantril(a)redhat.com fbricon(a)redhat.com slkabanovich(a)gmail.com
> Notifying upstream projects of job completion
> Finished: FAILURE
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1030) Allow for target platform deployment to nexus staging or release
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-1030:
---------------------------------
Summary: Allow for target platform deployment to nexus staging or release
Key: JBTIS-1030
URL: https://issues.jboss.org/browse/JBTIS-1030
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: target-platform
Affects Versions: 4.4.1.CR2-TP
Reporter: Paul Leacu
Assignee: Paul Leacu
Fix For: 4.4.1.Final-TP
User hudson in Jenkins does not have deploy (write) access to the nexus release repo but it does have access to deploy to the nexus staging repo. Modify the JBTIS TP pom to allow the user to specify which repo to deploy to.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23813) Package Explorer: context menu can cause exception on project that has svn metadata but erroneously configured SVN provider
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23813?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23813:
-------------------------------------
Summary: Package Explorer: context menu can cause exception on project that has svn metadata but erroneously configured SVN provider (was: Pacakge Explorer: context menu can cause exception on project that has svn metadata but erroneously configured SVN provider)
> Package Explorer: context menu can cause exception on project that has svn metadata but erroneously configured SVN provider
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23813
> URL: https://issues.jboss.org/browse/JBIDE-23813
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Labels: openshift_v2
> Fix For: 4.4.3.Final
>
>
> created from aeri. The following stack trace is reported:
> {code}
> Bundle: org.eclipse.team.core 3.7.100.v20150203-1452
> Message: Could not instantiate provider org.tigris.subversion.subclipse.core.svnnature for project pef.client.
> Exception:
> org.eclipse.team.core.TeamException: Could not instantiate provider org.tigris.subversion.subclipse.core.svnnature for project pef.client.
> at org.eclipse.team.core.RepositoryProvider.mapNewProvider(RepositoryProvider.java:165)
> at org.eclipse.team.core.RepositoryProvider.mapExistingProvider(RepositoryProvider.java:235)
> at org.eclipse.team.core.RepositoryProvider.getProvider(RepositoryProvider.java:507)
> at org.jboss.tools.openshift.egit.core.EGitUtils.isShared(EGitUtils.java:132)
> at org.jboss.tools.openshift.express.internal.ui.propertytester.ProjectPropertyTester.isIfSharedIsEGit(ProjectPropertyTester.java:48)
> at org.jboss.tools.openshift.express.internal.ui.propertytester.ProjectPropertyTester.test(ProjectPropertyTester.java:33)
> at org.eclipse.core.internal.expressions.Property.test(Property.java:58)
> at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:100)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:31)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:106)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:199)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:31)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:75)
> at org.eclipse.e4.ui.internal.workbench.ContributionsAnalyzer.isVisible(ContributionsAnalyzer.java:256)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.computeVisibility(ContributionRecord.java:166)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.updateVisibility(ContributionRecord.java:96)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:188)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:199)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerShowProcessor.showMenu(MenuManagerShowProcessor.java:230)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerShowProcessor.menuAboutToHide(MenuManagerShowProcessor.java:110)
> at org.eclipse.jface.internal.MenuManagerEventHelper.showEventPostHelper(MenuManagerEventHelper.java:92)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:467)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23813) Package Explorer: context menu can cause exception when selected project has svn metadata but erroneously configured/missing SVN provider
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23813?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23813:
-------------------------------------
Summary: Package Explorer: context menu can cause exception when selected project has svn metadata but erroneously configured/missing SVN provider (was: Package Explorer: context menu can cause exception on project that has svn metadata but erroneously configured SVN provider)
> Package Explorer: context menu can cause exception when selected project has svn metadata but erroneously configured/missing SVN provider
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23813
> URL: https://issues.jboss.org/browse/JBIDE-23813
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Labels: openshift_v2
> Fix For: 4.4.3.Final
>
>
> created from aeri. The following stack trace is reported:
> {code}
> Bundle: org.eclipse.team.core 3.7.100.v20150203-1452
> Message: Could not instantiate provider org.tigris.subversion.subclipse.core.svnnature for project pef.client.
> Exception:
> org.eclipse.team.core.TeamException: Could not instantiate provider org.tigris.subversion.subclipse.core.svnnature for project pef.client.
> at org.eclipse.team.core.RepositoryProvider.mapNewProvider(RepositoryProvider.java:165)
> at org.eclipse.team.core.RepositoryProvider.mapExistingProvider(RepositoryProvider.java:235)
> at org.eclipse.team.core.RepositoryProvider.getProvider(RepositoryProvider.java:507)
> at org.jboss.tools.openshift.egit.core.EGitUtils.isShared(EGitUtils.java:132)
> at org.jboss.tools.openshift.express.internal.ui.propertytester.ProjectPropertyTester.isIfSharedIsEGit(ProjectPropertyTester.java:48)
> at org.jboss.tools.openshift.express.internal.ui.propertytester.ProjectPropertyTester.test(ProjectPropertyTester.java:33)
> at org.eclipse.core.internal.expressions.Property.test(Property.java:58)
> at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:100)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:31)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:106)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:199)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:31)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:75)
> at org.eclipse.e4.ui.internal.workbench.ContributionsAnalyzer.isVisible(ContributionsAnalyzer.java:256)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.computeVisibility(ContributionRecord.java:166)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.updateVisibility(ContributionRecord.java:96)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:188)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:199)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerShowProcessor.showMenu(MenuManagerShowProcessor.java:230)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerShowProcessor.menuAboutToHide(MenuManagerShowProcessor.java:110)
> at org.eclipse.jface.internal.MenuManagerEventHelper.showEventPostHelper(MenuManagerEventHelper.java:92)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:467)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months