[JBoss JIRA] (JBIDE-22328) Connection wizard: 'OpenShift 3' is missing on drop down menu 'Server Type' (OpenShift 3 plugins wont get installed)
by Xia Zhao (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22328?page=com.atlassian.jira.plugi... ]
Xia Zhao commented on JBIDE-22328:
----------------------------------
[~adietish] Thanks for the info -- Confirmed that with my Eclipse Neon Milestone 4 (4.6.0M5), after updated it with http://download.jboss.org/jbosstools/neon/snapshots/updates/ , the original issue disappeared.
Thanks,
Xia
> Connection wizard: 'OpenShift 3' is missing on drop down menu 'Server Type' (OpenShift 3 plugins wont get installed)
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22328
> URL: https://issues.jboss.org/browse/JBIDE-22328
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: JBT: 3.2.0.Alpha1-v20160509-1836-B1291
> Eclipse version: Neon Milestone 4 (4.6.0M5)
> Reporter: Xia Zhao
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha2
>
> Attachments: installation-works.png, jetty-plugin-missing.png, jetty-websocket-client.png, neon-update-site.png, openshift-plugins-version.png, Screenshot from 2016-05-11 13-40-59.png, software-update.png
>
>
> After JBT 3.2.0.Alpha1-v20160509-1836-B1291 is installed successfully, run the New Connection Wizard, menuitem 'OpenShift 3' is missing on drop down menu 'Server Type' of 'New OpenShift Connection' window
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22284) ConcurrentModificationException below ArquillianUIUtil.getActiveType (thrown in FeatureMapUtil$BasicFeatureEIterator.checkModCount)
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22284?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-22284:
---------------------------------------
Now SelectionConverter.getElementAtOffset is called only when a compilation unit is consistent, i.e., when reconciling a compilation unit doesn't call Java EE validator or cause any notifications.
I can't test the issue because I haven't succeeded to reproduce it.
> ConcurrentModificationException below ArquillianUIUtil.getActiveType (thrown in FeatureMapUtil$BasicFeatureEIterator.checkModCount)
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22284
> URL: https://issues.jboss.org/browse/JBIDE-22284
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.0.Alpha2
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.util.ConcurrentModificationException: null
> at org.eclipse.emf.ecore.util.FeatureMapUtil$BasicFeatureEIterator.checkModCount(FeatureMapUtil.java:555)
> at org.eclipse.emf.ecore.util.FeatureMapUtil$BasicFeatureEIterator.next(FeatureMapUtil.java:373)
> at org.eclipse.jst.jee.model.internal.mergers.EjbJarMerger.mergeSessionBeans(EjbJarMerger.java:145)
> at org.eclipse.jst.jee.model.internal.mergers.EjbJarMerger.process(EjbJarMerger.java:74)
> at org.eclipse.jst.jee.model.internal.mergers.EjbJarMerger.process(EjbJarMerger.java:79)
> at org.eclipse.jst.jee.model.internal.EJB3MergedModelProvider.mergeWithModel(EJB3MergedModelProvider.java:214)
> at org.eclipse.jst.jee.model.internal.EJB3MergedModelProvider.merge(EJB3MergedModelProvider.java:204)
> at org.eclipse.jst.jee.model.internal.EJB3MergedModelProvider.internalModelChanged(EJB3MergedModelProvider.java:174)
> at org.eclipse.jst.jee.model.internal.EJB3MergedModelProvider.annotationModelChanged(EJB3MergedModelProvider.java:151)
> at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider$AnnotationModelListener.modelsChanged(AbstractMergedModelProvider.java:83)
> at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider$1.run(AbstractAnnotationModelProvider.java:189)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.notifyListeners(AbstractAnnotationModelProvider.java:184)
> at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.notifyListeners(AbstractAnnotationModelProvider.java:157)
> at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.internalPostReconcile(AbstractAnnotationModelProvider.java:467)
> at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.elementChanged(AbstractAnnotationModelProvider.java:446)
> at org.eclipse.jdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1662)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1652)
> at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1504)
> at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1463)
> at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:770)
> at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:789)
> at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1250)
> at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1211)
> at org.eclipse.jdt.internal.corext.util.JavaModelUtil.reconcile(JavaModelUtil.java:609)
> at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:283)
> at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:199)
> at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:183)
> at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.getActiveType(ArquillianUIUtil.java:182)
> at org.jboss.tools.arquillian.ui.internal.commands.ArquillianPropertyTester.test(ArquillianPropertyTester.java:62)
> 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.AdaptExpression.evaluate(AdaptExpression.java:106)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateOr(CompositeExpression.java:68)
> at org.eclipse.core.internal.expressions.OrExpression.evaluate(OrExpression.java:22)
> 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.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.ui.internal.WorkbenchWindow$8.run(WorkbenchWindow.java:707)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155)
> {noformat}
> Bundles:
> | org.eclipse.core.expressions | 3.5.0.v20150421-2214 | 3.5.0.v20150421-2214 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.eclipse.e4.ui.workbench | 1.3.1.v20160203-0951 | 1.3.1.v20160203-0951 |
> | org.eclipse.e4.ui.workbench.renderers.swt | 0.13.0.v20150901-1347 | 0.13.0.v20150901-1347 |
> | org.eclipse.emf | 2.6.0.v20160208-0841 | 2.6.0.v20160208-0841 |
> | org.eclipse.emf.ecore | 2.11.2.v20160208-0816 | 2.11.2.v20160208-0816 |
> | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.11.2.v20160212-1500 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 |
> | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 |
> | org.eclipse.jst.jee | 1.0.700.v201404092004 | 1.0.700.v201404092004 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> | org.jboss.tools.arquillian.ui | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571f1795e4b08bd809...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22362:
-------------------------------------
Summary: Server Adapter: Static changes done to nodejs application are not visible (was: Static changes done to nodejs application are not visible)
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, server_adapter
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22362:
-------------------------------------
Labels: openshift_v3 server_adapter (was: openshift_v3)
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, server_adapter
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22364) Tests: TabFolderTraverseListenerTest.testTabFolderTraverseListener fails on MacOS
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22364?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22364:
-------------------------------------
Description:
org.jboss.tools.openshift.test.ui.wizard.newapp.TabFolderTraverseListenerTest.testTabFolderTraverseListener fails consistently on MacOS (not in Windows) in jenkins: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift...
The build has usage disabled via maven flag like it is in the main build:
{code}
-Dusage_reporting_enabled=false
{code}
the maven command line that executes the build in macos is the following:
{code}
[macosx] $ /qa/tools/opt/apache-maven-3.1.1/bin/mvn -DTARGET_PLATFORM_VERSION=4.60.0.Alpha1-SNAPSHOT -DTARGET_PLATFORM_VERSION_MAXIMUM=4.60.0.Alpha1-SNAPSHOT -Djdk=jdk1.8 -Dlabel_exp=macosx "-DMAVEN_FLAGS=-B -U -fae -e" -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true -Dmaven.repo.local=/mnt/hudson_workspace/workspace/jbosstools-openshift_master_otherOS/jdk/jdk1.8/label_exp/macosx/.repository clean verify -B -U -fae -e -Dusage_reporting_enabled=false -DTARGET_PLATFORM_VERSION=4.60.0.Alpha1-SNAPSHOT
{code}
was:
org.jboss.tools.openshift.test.ui.wizard.newapp.TabFolderTraverseListenerTest.testTabFolderTraverseListener fails currently on MacOS in jenkins: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift...
The build has usage disabled via maven flag like it is in the main build:
{code}
-Dusage_reporting_enabled=false
{code}
the maven command line that executes the build in macos is the following:
{code}
[macosx] $ /qa/tools/opt/apache-maven-3.1.1/bin/mvn -DTARGET_PLATFORM_VERSION=4.60.0.Alpha1-SNAPSHOT -DTARGET_PLATFORM_VERSION_MAXIMUM=4.60.0.Alpha1-SNAPSHOT -Djdk=jdk1.8 -Dlabel_exp=macosx "-DMAVEN_FLAGS=-B -U -fae -e" -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true -Dmaven.repo.local=/mnt/hudson_workspace/workspace/jbosstools-openshift_master_otherOS/jdk/jdk1.8/label_exp/macosx/.repository clean verify -B -U -fae -e -Dusage_reporting_enabled=false -DTARGET_PLATFORM_VERSION=4.60.0.Alpha1-SNAPSHOT
{code}
> Tests: TabFolderTraverseListenerTest.testTabFolderTraverseListener fails on MacOS
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22364
> URL: https://issues.jboss.org/browse/JBIDE-22364
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha2
>
>
> org.jboss.tools.openshift.test.ui.wizard.newapp.TabFolderTraverseListenerTest.testTabFolderTraverseListener fails consistently on MacOS (not in Windows) in jenkins: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift...
> The build has usage disabled via maven flag like it is in the main build:
> {code}
> -Dusage_reporting_enabled=false
> {code}
> the maven command line that executes the build in macos is the following:
> {code}
> [macosx] $ /qa/tools/opt/apache-maven-3.1.1/bin/mvn -DTARGET_PLATFORM_VERSION=4.60.0.Alpha1-SNAPSHOT -DTARGET_PLATFORM_VERSION_MAXIMUM=4.60.0.Alpha1-SNAPSHOT -Djdk=jdk1.8 -Dlabel_exp=macosx "-DMAVEN_FLAGS=-B -U -fae -e" -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true -Dmaven.repo.local=/mnt/hudson_workspace/workspace/jbosstools-openshift_master_otherOS/jdk/jdk1.8/label_exp/macosx/.repository clean verify -B -U -fae -e -Dusage_reporting_enabled=false -DTARGET_PLATFORM_VERSION=4.60.0.Alpha1-SNAPSHOT
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months