[JBoss JIRA] (JBIDE-24523) compilation error in org.jboss.tools.openshift.ui.bot.test: LOCAL_TEMPLATE cannot be resolved or is not a field
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24523?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-24523.
------------------------------
> compilation error in org.jboss.tools.openshift.ui.bot.test: LOCAL_TEMPLATE cannot be resolved or is not a field
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24523
> URL: https://issues.jboss.org/browse/JBIDE-24523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests, openshift
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Radim Hopp
> Fix For: 4.5.0.AM1
>
>
> {code}
> 20:33:49 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:1.0.0:compile (default-compile) on project org.jboss.tools.openshift.ui.bot.test: Compilation failure: Compilation failure:
> 20:33:49 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.openshift.ui.bot.test/src/org/jboss/tools/openshift/ui/bot/test/application/v3/basic/NewApplicationWizardHandlingTest.java:[81]
> 20:33:49 [ERROR] new DefaultTabItem(OpenShiftLabel.TextLabels.LOCAL_TEMPLATE).activate();
> 20:33:49 [ERROR] ^^^^^^^^^^^^^^
> 20:33:49 [ERROR] LOCAL_TEMPLATE cannot be resolved or is not a field
> 20:33:49 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.openshift.ui.bot.test/src/org/jboss/tools/openshift/ui/bot/test/application/v3/basic/NewApplicationWizardHandlingTest.java:[132]
> 20:33:49 [ERROR] new DefaultTabItem(OpenShiftLabel.TextLabels.LOCAL_TEMPLATE).activate();
> 20:33:49 [ERROR] ^^^^^^^^^^^^^^
> 20:33:49 [ERROR] LOCAL_TEMPLATE cannot be resolved or is not a field
> 20:33:49 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.openshift.ui.bot.test/src/org/jboss/tools/openshift/ui/bot/test/application/v3/basic/NewApplicationWizardHandlingTest.java:[142]
> 20:33:49 [ERROR] new DefaultTabItem(OpenShiftLabel.TextLabels.LOCAL_TEMPLATE).activate();
> 20:33:49 [ERROR] ^^^^^^^^^^^^^^
> 20:33:49 [ERROR] LOCAL_TEMPLATE cannot be resolved or is not a field
> 20:33:49 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.openshift.ui.bot.test/src/org/jboss/tools/openshift/ui/bot/test/application/v3/basic/NewApplicationWizardHandlingTest.java:[148]
> 20:33:49 [ERROR] new DefaultTabItem(OpenShiftLabel.TextLabels.LOCAL_TEMPLATE).activate();
> 20:33:49 [ERROR] ^^^^^^^^^^^^^^
> 20:33:49 [ERROR] LOCAL_TEMPLATE cannot be resolved or is not a field
> 20:33:49 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.openshift.ui.bot.test/src/org/jboss/tools/openshift/ui/bot/test/application/v3/basic/NewApplicationWizardHandlingTest.java:[196]
> 20:33:49 [ERROR] new DefaultTabItem(OpenShiftLabel.TextLabels.LOCAL_TEMPLATE).activate();
> 20:33:49 [ERROR] ^^^^^^^^^^^^^^
> 20:33:49 [ERROR] LOCAL_TEMPLATE cannot be resolved or is not a field
> 20:33:49 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.openshift.ui.bot.test/src/org/jboss/tools/openshift/ui/bot/test/application/v3/create/CreateApplicationFromTemplateTest.java:[138]
> 20:33:49 [ERROR] new DefaultTabItem(OpenShiftLabel.TextLabels.LOCAL_TEMPLATE).activate();
> 20:33:49 [ERROR] ^^^^^^^^^^^^^^
> 20:33:49 [ERROR] LOCAL_TEMPLATE cannot be resolved or is not a field
> 20:33:49 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.openshift.ui.bot.test/src/org/jboss/tools/openshift/ui/bot/test/application/v3/create/CreateApplicationFromTemplateTest.java:[161]
> 20:33:49 [ERROR] new DefaultTabItem(OpenShiftLabel.TextLabels.LOCAL_TEMPLATE).activate();
> 20:33:49 [ERROR] ^^^^^^^^^^^^^^
> 20:33:49 [ERROR] LOCAL_TEMPLATE cannot be resolved or is not a field
> 20:33:49 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.tools.openshift.ui.bot.test/src/org/jboss/tools/openshift/ui/bot/test/application/v3/create/CreateApplicationFromTemplateTest.java:[174]
> 20:33:49 [ERROR] new DefaultTabItem(OpenShiftLabel.TextLabels.LOCAL_TEMPLATE).activate();
> 20:33:49 [ERROR] ^^^^^^^^^^^^^^
> 20:33:49 [ERROR] LOCAL_TEMPLATE cannot be resolved or is not a field
> 20:33:49 [ERROR] 8 problems (8 errors)
> {code}
> -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (JBIDE-24438) Server adapter: JMX connection is not working for OpenShift instance
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24438?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-24438:
-----------------------------------------
{quote}I'm sorry, but I really don't understand the steps to replicate here. {quote}
ok, steps were not very precised but I reported it quickly when I was in a conference. I thought that there was enough information.
{quote}
What do you mean by "connect to open.paas.redhat.com with server adapters" ??
Do you mean create an openshift connection to open.paas.redhat.com and then create a server adapter from one of the projects there?{quote}
Yes
{quote}Which project?{quote}
whatever projects providing a JMX connection. I know that the FIS ones are providing one.
{quote}
What is open.paas.redhat.com?{quote}
It is the internal Red Hat OpenShift server.
{quote}Is it the same as openshift.io?{quote}
no.
openshift.io was not released when i reported the issue and I still have no access to it but I guess that it contains also on OpenSHift instance to which we can connect.
{quote}What credentials does this use?{quote}
everything is explained on the login page (that you can access when you are logged in to the Red Hat vpn.
I provided an example with open.paas.redhat.com but I think that it applies to all OpenShift instance that are not using a specific port number to connect to.
I cannot provide a screencast for now because it seems that FIS is broken of open.paas.redhat.com and i don't have time to investigate which other kind of image I can use.
{noformat}
Receiving source from STDIN as archive ...
==================================================================
Starting S2I Java Build .....
S2I source build with plain binaries detected
Copying binaries from /tmp/src to /deployments ...
cp: cannot stat '/tmp/src/*': No such file or directory
Aborting due to error code 1 for copying /tmp/src to /deployments
error: build error: non-zero (13) exit code from registry.access.redhat.com/jboss-fuse-6/fis-java-openshift:2.0-5
{noformat}
> Server adapter: JMX connection is not working for OpenShift instance
> ---------------------------------------------------------------------
>
> Key: JBIDE-24438
> URL: https://issues.jboss.org/browse/JBIDE-24438
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Labels: jmx, jolokia, openshift_v3, server_adapter
> Fix For: 4.5.0.AM1
>
>
> such as open.paas.redhat.com
> {noformat}
> java.io.IOException: org.jolokia.client.exception.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.jolokia.client.exception.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.jolokia.client.J4pClient.mapException(J4pClient.java:330)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:198)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
> ... 4 more
> Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:150)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:190)
> ... 7 more
> Caused by: java.net.SocketTimeoutException: connect timed out
> at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
> at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
> at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
> at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141)
> ... 18 more
> {noformat}
> we can notice that the url used is https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...
> It should not contain the port 8443
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (JBTIS-1118) Use existing RedDeer implementation for opening views/preferences/editors
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-1118:
----------------------------------------
Summary: Use existing RedDeer implementation for opening views/preferences/editors
Key: JBTIS-1118
URL: https://issues.jboss.org/browse/JBTIS-1118
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: Fuse IDE, QE
Affects Versions: 4.3.3.Final
Reporter: Andrej Podhradsky
Assignee: Tomáš Sedmík
Priority: Blocker
Fix For: 4.3.3.Final
We need to reuse existing RedDeer implementation for opening and closing views/preferences/editors.
For example, the class ConsolePreferencePage where we use our own implementation. Note that in Oxygen lots of labels were changed and these changes are adapted in RedDeer 1.2.2.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (JBIDE-24377) Could not find artifact org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24377?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-24377.
---------------------------------
Job is green, closing.
> Could not find artifact org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-24377
> URL: https://issues.jboss.org/browse/JBIDE-24377
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> {code}
> 14:38:32 [INFO] org.jboss.ide.eclipse.as.management.wf11 ........... FAILURE [ 14.669 s]
> 14:38:32 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.7:copy (get-libs) on project org.jboss.ide.eclipse.as.management.wf11: Unable to find artifact. Could not find artifact org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT in jboss-releases (https://repository.jboss.org/nexus/content/repositories/releases)
> 14:38:32 [ERROR]
> 14:38:32 [ERROR] Try downloading the file manually from the project website.
> 14:38:32 [ERROR]
> 14:38:32 [ERROR] Then, install it using the command:
> 14:38:32 [ERROR] mvn install:install-file -DgroupId=org.wildfly.core -DartifactId=wildfly-controller-client -Dversion=3.0.0.Beta16-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
> 14:38:32 [ERROR]
> 14:38:32 [ERROR] Alternatively, if you host your own repository you can deploy the file there:
> 14:38:32 [ERROR] mvn deploy:deploy-file -DgroupId=org.wildfly.core -DartifactId=wildfly-controller-client -Dversion=3.0.0.Beta16-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> 14:38:32 [ERROR]
> 14:38:32 [ERROR]
> 14:38:32 [ERROR] org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT
> 14:38:32 [ERROR]
> 14:38:32 [ERROR] from the specified remote repositories:
> 14:38:32 [ERROR] redhat-ea-repository (https://maven.repository.redhat.com/earlyaccess/all/, releases=true, snapshots=false),
> 14:38:32 [ERROR] redhat-ga-repository (http://maven.repository.redhat.com/ga/, releases=true, snapshots=false),
> 14:38:32 [ERROR] jboss-releases (https://repository.jboss.org/nexus/content/repositories/releases, releases=true, snapshots=true),
> 14:38:32 [ERROR] jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/, releases=true, snapshots=true),
> 14:38:32 [ERROR] jbosstools-experiments (https://repository.jboss.org/nexus/content/repositories/jbosstools-experi..., releases=true, snapshots=true),
> 14:38:32 [ERROR] jbosstools-base (http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-b..., releases=false, snapshots=false),
> 14:38:32 [ERROR] jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/, releases=true, snapshots=true),
> 14:38:32 [ERROR] jboss-ga-repository (http://maven.repository.redhat.com/ga/, releases=true, snapshots=true),
> 14:38:32 [ERROR] central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false)
> 14:38:32 [ERROR] -> [Help 1]
> {code}
> -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (JBIDE-24516) I am not able to see the design of openshift java form
by jyoti tumsare (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24516?page=com.atlassian.jira.plugi... ]
jyoti tumsare commented on JBIDE-24516:
---------------------------------------
Thank you .. and sorry for trouble.
> I am not able to see the design of openshift java form
> ------------------------------------------------------
>
> Key: JBIDE-24516
> URL: https://issues.jboss.org/browse/JBIDE-24516
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.4.Final
> Environment: sir, I have build jbosstools-openshift.4.4.4.Final successfully.I just want to see the design of java form.i am unable to see it.I installed swt , jface and windowsbuilder jar. I am able to see the other project form design but when it comes to openshift feature I am unable to see the design of java form. please help me
> Reporter: jyoti tumsare
> Assignee: Andre Dietisheim
> Fix For: 4.5.0.AM1
>
> Attachments: opengui.png, opengui.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years