[JBoss JIRA] (JBIDE-24748) Enable Show In Console for cdk 3
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24748?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24748:
-------------------------------------
Did some more testing, tried to prepare a patch for upstream, but, it didn't work. Here's why:
If I make the upstream actions re-check their enablement when a server state changes, sounds like a good idea, no? Except, the server is set to 'starting...' before it actually launches any command. So, CDK is set to 'starting', state change fires an event, the UI actions hear the event, check if the server is not stopped (check), check if the server has a launch (check), check if the launch has processes (fail), and set enablement to false.
Basically, the only way to get this to show up is to re-click on your selection. Right now you're probably re-right-clicking, which doesn't trigger the selection change event. The only way to get show in console to actually show up is to right-click your server, 'start' it, then CLICK your server, then RIGHT-CLICK your server again.
Extensive testing, and that's the only way. No amount of code changes on my part will fix this ;) SORRY!
> Enable Show In Console for cdk 3
> --------------------------------
>
> Key: JBIDE-24748
> URL: https://issues.jboss.org/browse/JBIDE-24748
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> CDK 2 used the Terminal view, CDK 3 switched back to usiong Console view. So Show In Console on the server adapter should be enabled.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4454) Path to JDK needs to be updated after every update of JDK
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4454?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-4454:
--------------------------------
Assignee: Josef Kopriva (was: Nick Boldt)
Resolution: Done
> Path to JDK needs to be updated after every update of JDK
> ---------------------------------------------------------
>
> Key: JBDS-4454
> URL: https://issues.jboss.org/browse/JBDS-4454
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: build, installer
> Affects Versions: 11.0.0.AM1
> Environment: Fedora 26
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Fix For: 11.0.0.GA
>
> Attachments: image-2017-06-30-11-01-40-783.png, jdk_selected_alternatives.png, screenshot-1.png
>
>
> After every update of JDK, path to JDK in file devstudio.ini needs to be updated. This does not happening in Eclipse.
> !image-2017-06-30-11-01-40-783.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4454) Path to JDK needs to be updated after every update of JDK
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4454?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4454:
----------------------------------
[~dgolovin] OK, thanks. I'll resolve this so [~jkopriva] can review the change.
Note that I didn't test this on Win or OSX, only on F24.
> Path to JDK needs to be updated after every update of JDK
> ---------------------------------------------------------
>
> Key: JBDS-4454
> URL: https://issues.jboss.org/browse/JBDS-4454
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: build, installer
> Affects Versions: 11.0.0.AM1
> Environment: Fedora 26
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
> Fix For: 11.0.0.GA
>
> Attachments: image-2017-06-30-11-01-40-783.png, jdk_selected_alternatives.png, screenshot-1.png
>
>
> After every update of JDK, path to JDK in file devstudio.ini needs to be updated. This does not happening in Eclipse.
> !image-2017-06-30-11-01-40-783.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4454) Path to JDK needs to be updated after every update of JDK
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4454?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4454:
-------------------------------------
Preventing it would affect both Windows and Linux installations, right? That means DevSuite Installer would not be able to start DevStudio when DevStudio and OpenJDK installed together on Windows. I'd rather keep adding -vm for now, because changes might broke other tools behavior.
> Path to JDK needs to be updated after every update of JDK
> ---------------------------------------------------------
>
> Key: JBDS-4454
> URL: https://issues.jboss.org/browse/JBDS-4454
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: build, installer
> Affects Versions: 11.0.0.AM1
> Environment: Fedora 26
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
> Fix For: 11.0.0.GA
>
> Attachments: image-2017-06-30-11-01-40-783.png, jdk_selected_alternatives.png, screenshot-1.png
>
>
> After every update of JDK, path to JDK in file devstudio.ini needs to be updated. This does not happening in Eclipse.
> !image-2017-06-30-11-01-40-783.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24534) Aeri connection problems on startup of devstudio / lucene issue?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24534?page=com.atlassian.jira.plugi... ]
Nick Boldt resolved JBIDE-24534.
--------------------------------
Resolution: Cannot Reproduce Bug
Cannot reproduce using 11.0.0.AM2 from the staging site. Must have been fixed by moving to a newer version of Aeri.
> Aeri connection problems on startup of devstudio / lucene issue?
> ----------------------------------------------------------------
>
> Key: JBIDE-24534
> URL: https://issues.jboss.org/browse/JBIDE-24534
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aeri, central-update
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.Final
>
>
> Having installed devstudio 11.0.0.AM1 into Oxygen.0.M7 JavaEE EPP bundle on Linux x64 (Fedora 24), I tried to install something from Central and instead got an AERI error:
> {code}
> !ENTRY org.eclipse.epp.logging.aeri.ide 2 17 2017-06-02 15:15:10.111
> !MESSAGE Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.5.v20170531-0951
> !STACK 0
> org.apache.http.conn.ConnectTimeoutException: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] 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:55)
> at org.apache.http.client.fluent.Request.internalExecute(Request.java:173)
> at org.apache.http.client.fluent.Executor.execute(Executor.java:262)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.request(IO.java:170)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.refreshConfiguration(IO.java:64)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.startUp(ServerConnection.java:124)
> at com.google.common.util.concurrent.AbstractIdleService$2$1.run(AbstractIdleService.java:54)
> at com.google.common.util.concurrent.Callables$3.run(Callables.java:93)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.SocketTimeoutException: connect timed out
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24534) Aeri connection problems on startup of devstudio / lucene issue?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24534?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-24534 at 7/27/17 4:02 PM:
-------------------------------------------------------------
Cannot reproduce using 11.0.0.AM2 from the staging site above, and the Oxygen.0 JavaEE bundle (rather than M7). Must have been fixed by moving to a newer version of Aeri.
was (Author: nickboldt):
Cannot reproduce using 11.0.0.AM2 from the staging site. Must have been fixed by moving to a newer version of Aeri.
> Aeri connection problems on startup of devstudio / lucene issue?
> ----------------------------------------------------------------
>
> Key: JBIDE-24534
> URL: https://issues.jboss.org/browse/JBIDE-24534
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aeri, central-update
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.Final
>
>
> Having installed devstudio 11.0.0.AM1 into Oxygen.0.M7 JavaEE EPP bundle on Linux x64 (Fedora 24), I tried to install something from Central and instead got an AERI error:
> {code}
> !ENTRY org.eclipse.epp.logging.aeri.ide 2 17 2017-06-02 15:15:10.111
> !MESSAGE Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.5.v20170531-0951
> !STACK 0
> org.apache.http.conn.ConnectTimeoutException: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] 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:55)
> at org.apache.http.client.fluent.Request.internalExecute(Request.java:173)
> at org.apache.http.client.fluent.Executor.execute(Executor.java:262)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.request(IO.java:170)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.refreshConfiguration(IO.java:64)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.startUp(ServerConnection.java:124)
> at com.google.common.util.concurrent.AbstractIdleService$2$1.run(AbstractIdleService.java:54)
> at com.google.common.util.concurrent.Callables$3.run(Callables.java:93)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.SocketTimeoutException: connect timed out
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24534) Aeri connection problems on startup of devstudio / lucene issue?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24534?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24534:
-------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.x)
> Aeri connection problems on startup of devstudio / lucene issue?
> ----------------------------------------------------------------
>
> Key: JBIDE-24534
> URL: https://issues.jboss.org/browse/JBIDE-24534
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aeri, central-update
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.Final
>
>
> Having installed devstudio 11.0.0.AM1 into Oxygen.0.M7 JavaEE EPP bundle on Linux x64 (Fedora 24), I tried to install something from Central and instead got an AERI error:
> {code}
> !ENTRY org.eclipse.epp.logging.aeri.ide 2 17 2017-06-02 15:15:10.111
> !MESSAGE Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.5.v20170531-0951
> !STACK 0
> org.apache.http.conn.ConnectTimeoutException: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] 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:55)
> at org.apache.http.client.fluent.Request.internalExecute(Request.java:173)
> at org.apache.http.client.fluent.Executor.execute(Executor.java:262)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.request(IO.java:170)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.refreshConfiguration(IO.java:64)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.startUp(ServerConnection.java:124)
> at com.google.common.util.concurrent.AbstractIdleService$2$1.run(AbstractIdleService.java:54)
> at com.google.common.util.concurrent.Callables$3.run(Callables.java:93)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.SocketTimeoutException: connect timed out
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months