[JBoss JIRA] (JBTIS-652) Adapt SAP tests according to the changes made in new Camel editor
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-652?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBTIS-652:
-----------------------------------------
[~tsedmik] any idea what could be wrong here?
> Adapt SAP tests according to the changes made in new Camel editor
> -----------------------------------------------------------------
>
> Key: JBTIS-652
> URL: https://issues.jboss.org/browse/JBTIS-652
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: Fuse IDE, QE
> Affects Versions: 9.0.0.CR1
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
>
> I'm still getting the following NPE when I try to add a component to the route
> {code}
> java.lang.NullPointerException
> at org.jboss.reddeer.gef.handler.EditPartHandler.getFigure(EditPartHandler.java:83)
> at org.jboss.reddeer.gef.impl.editpart.AbstractEditPart.getFigure(AbstractEditPart.java:89)
> at org.jboss.tools.fuse.reddeer.editor.CamelComponentEditPart.getBounds(CamelComponentEditPart.java:22)
> at org.jboss.tools.fuse.reddeer.editor.CamelEditor.getInEditorCoords(CamelEditor.java:608)
> at org.jboss.tools.fuse.reddeer.editor.CamelEditor.addCamelComponent(CamelEditor.java:150)
> at org.jboss.tools.fuse.ui.bot.test.SAPComponentTest.testSAPTRFCServer(SAPComponentTest.java:194)
> 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:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.jboss.reddeer.junit.internal.runner.statement.RunTestMethod.evaluate(RunTestMethod.java:36)
> at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:69)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeTestExtensions.evaluate(RunIBeforeTestExtensions.java:63)
> at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterTestExtensions.evaluate(RunIAfterTestExtensions.java:51)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.runChild(RequirementsRunner.java:165)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:69)
> at org.jboss.reddeer.junit.internal.runner.statement.FulfillRequirementsStatement.evaluate(FulfillRequirementsStatement.java:35)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeClassExtensions.evaluate(RunIBeforeClassExtensions.java:60)
> at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58)
> at org.jboss.reddeer.junit.internal.runner.statement.CleanUpRequirementStatement.evaluate(CleanUpRequirementStatement.java:34)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:48)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.run(RequirementsRunner.java:146)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at org.jboss.reddeer.eclipse.core.RemotePluginTestRunner.main(RemotePluginTestRunner.java:58)
> at org.jboss.reddeer.eclipse.core.UITestApplication.runTests(UITestApplication.java:115)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:73)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-652) Adapt SAP tests according to the changes made in new Camel editor
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-652:
---------------------------------------
Summary: Adapt SAP tests according to the changes made in new Camel editor
Key: JBTIS-652
URL: https://issues.jboss.org/browse/JBTIS-652
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: Fuse IDE, QE
Affects Versions: 9.0.0.CR1
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
I'm still getting the following NPE when I try to add a component to the route
{code}
java.lang.NullPointerException
at org.jboss.reddeer.gef.handler.EditPartHandler.getFigure(EditPartHandler.java:83)
at org.jboss.reddeer.gef.impl.editpart.AbstractEditPart.getFigure(AbstractEditPart.java:89)
at org.jboss.tools.fuse.reddeer.editor.CamelComponentEditPart.getBounds(CamelComponentEditPart.java:22)
at org.jboss.tools.fuse.reddeer.editor.CamelEditor.getInEditorCoords(CamelEditor.java:608)
at org.jboss.tools.fuse.reddeer.editor.CamelEditor.addCamelComponent(CamelEditor.java:150)
at org.jboss.tools.fuse.ui.bot.test.SAPComponentTest.testSAPTRFCServer(SAPComponentTest.java:194)
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:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.jboss.reddeer.junit.internal.runner.statement.RunTestMethod.evaluate(RunTestMethod.java:36)
at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:69)
at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeTestExtensions.evaluate(RunIBeforeTestExtensions.java:63)
at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58)
at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterTestExtensions.evaluate(RunIAfterTestExtensions.java:51)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.runChild(RequirementsRunner.java:165)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:69)
at org.jboss.reddeer.junit.internal.runner.statement.FulfillRequirementsStatement.evaluate(FulfillRequirementsStatement.java:35)
at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeClassExtensions.evaluate(RunIBeforeClassExtensions.java:60)
at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58)
at org.jboss.reddeer.junit.internal.runner.statement.CleanUpRequirementStatement.evaluate(CleanUpRequirementStatement.java:34)
at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:48)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.run(RequirementsRunner.java:146)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at org.jboss.reddeer.eclipse.core.RemotePluginTestRunner.main(RemotePluginTestRunner.java:58)
at org.jboss.reddeer.eclipse.core.UITestApplication.runTests(UITestApplication.java:115)
at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:73)
at java.lang.Thread.run(Thread.java:745)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-649) Update org.jboss.tools.foundation.security.linux.feature to 1.2.1.Final
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-649?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBTIS-649:
-----------------------------------------
The old security bundle is in the JBDS-IS EA update site, please see the screenshot of the p2browser
> Update org.jboss.tools.foundation.security.linux.feature to 1.2.1.Final
> -----------------------------------------------------------------------
>
> Key: JBTIS-649
> URL: https://issues.jboss.org/browse/JBTIS-649
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: distribution
> Affects Versions: 9.0.0.CR1
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Minor
> Attachments: found1.png, jbdsis_security_bundle.png
>
>
> Currently, JBDS-IS 9.0.0.CR1 (and also the snapshot of CR1a) contains
> org.jboss.tools.foundation.security.linux 1.2.1.Beta2-v20160127-2129-B77
> but the JBDS 9.1.0.CR1a contains
> org.jboss.tools.foundation.security.linux 1.2.1.Final-v20160401-0436-B108
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-649) Update org.jboss.tools.foundation.security.linux.feature to 1.2.1.Final
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-649?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-649:
------------------------------------
Attachment: jbdsis_security_bundle.png
> Update org.jboss.tools.foundation.security.linux.feature to 1.2.1.Final
> -----------------------------------------------------------------------
>
> Key: JBTIS-649
> URL: https://issues.jboss.org/browse/JBTIS-649
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: distribution
> Affects Versions: 9.0.0.CR1
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Minor
> Attachments: found1.png, jbdsis_security_bundle.png
>
>
> Currently, JBDS-IS 9.0.0.CR1 (and also the snapshot of CR1a) contains
> org.jboss.tools.foundation.security.linux 1.2.1.Beta2-v20160127-2129-B77
> but the JBDS 9.1.0.CR1a contains
> org.jboss.tools.foundation.security.linux 1.2.1.Final-v20160401-0436-B108
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22134) Sometimes docker image data are not shown in Deploy to OpenShift wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22134?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-22134 at 4/8/16 10:00 AM:
----------------------------------------------------------------
[~jcantrill] For example, I was experiencing this issue when I tried to deploy openshift/wildfly-90-centos7 image to OpenShift. When inspecting the docker image the following is present in container config:
{code}"ExposedPorts": {
"8080/tcp": {}
},{code}
{code}"Env": [
"PATH=/opt/app-root/src/bin:/opt/app-root/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"STI_SCRIPTS_URL=image:///usr/libexec/s2i",
"STI_SCRIPTS_PATH=/usr/libexec/s2i",
"HOME=/opt/app-root/src",
"BASH_ENV=/opt/app-root/etc/scl_enable",
"ENV=/opt/app-root/etc/scl_enable",
"PROMPT_COMMAND=. /opt/app-root/etc/scl_enable",
"WILDFLY_VERSION=9.0.2",
"WILDFLY_VERSION_BIN=9.0.2.Final",
"MAVEN_VERSION=3.3.3"
],{code}
I think those are (meta)data we are using in wizard and somehow, sometimes they are not present in Deploy Docker Image to OpenShift wizard. Table containing env. vars and ports are empty in the wizard. This is happening when an image is already pulled locally. But so far, as I mentioned, I was not able to find a reliable way to reproduce it. I was not experiencing this when I was trying to use an image which has not been pulled yet. But it does not necessary mean it is a cause of it or it has something to do with that, but it could be related.
was (Author: mlabuda):
[~jcantrill] For example, I was experiencing this issue when I tried to deploy openshift/wildfly-90-centos7 image to OpenShift. When inspecting the docker image the following is present:
{code}"ExposedPorts": {
"8080/tcp": {}
},{code}
{code}"Env": [
"PATH=/opt/app-root/src/bin:/opt/app-root/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"STI_SCRIPTS_URL=image:///usr/libexec/s2i",
"STI_SCRIPTS_PATH=/usr/libexec/s2i",
"HOME=/opt/app-root/src",
"BASH_ENV=/opt/app-root/etc/scl_enable",
"ENV=/opt/app-root/etc/scl_enable",
"PROMPT_COMMAND=. /opt/app-root/etc/scl_enable",
"WILDFLY_VERSION=9.0.2",
"WILDFLY_VERSION_BIN=9.0.2.Final",
"MAVEN_VERSION=3.3.3"
],{code}
I think those are (meta)data we are using in wizard and somehow, sometimes they are not present in Deploy Docker Image to OpenShift wizard. Table containing env. vars and ports are empty in the wizard. This is happening when an image is already pulled locally. But so far, as I mentioned, I was not able to find a reliable way to reproduce it. I was not experiencing this when I was trying to use an image which has not been pulled yet. But it does not necessary mean it is a cause of it or it has something to do with that, but it could be related.
> Sometimes docker image data are not shown in Deploy to OpenShift wizard
> -----------------------------------------------------------------------
>
> Key: JBIDE-22134
> URL: https://issues.jboss.org/browse/JBIDE-22134
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
>
> Sometimes docker image data are not shown/processed in Deploy to OpenShift wizard. Environment variables, exposed ports etc. Unfortunately I don't have a way to reproduce it 100 %, I am not sure at the moment what is causing it, but when deploying a local docker image (image already pulled) to OpenShift, environment variables and exposed ports are empty, even though when using an image which has not been pulled yet, I have not spotted this at all.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years