October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-18696 at 10/27/14 7:24 AM: -------------------------------------------------------------------- I tried to replicate this using win8 and the exact same devenv (ec2-54-91-37-89.compute-1.amazonaws.com). I couldnt, I got the quickstarts right ahead (no restarting Eclipse/JBDS required): # ASSERT: make sure you have "-Djsse.enableSNIExtension=false" in your eclipse.ini (or jbdevstudio.ini) # EXEC: launch JBDS/Eclipse # EXEC: File->New->OpenShift->New Application # EXEC: New Connection, point it to ec2-54-91-37-89.compute-1.amazonaws.com and use some random credentials # EXEC: Look at the quickstart cathegory Result: It's fully popullated with entries (for me) !quickstarts-listed-win8.png! was (Author: adietish): I tried to replicate this using win8 and the exact same devenv (ec2-54-91-37-89.compute-1.amazonaws.com). I couldnt, I got the quickstarts right ahead: # ASSERT: make sure you have "-Djsse.enableSNIExtension=false" in your eclipse.ini (or jbdevstudio.ini) # EXEC: launch JBDS/Eclipse # EXEC: File->New->OpenShift->New Application # EXEC: New Connection, point it to ec2-54-91-37-89.compute-1.amazonaws.com and use some random credentials # EXEC: Look at the quickstart cathegory Result: It's fully popullated with entries (for me) !quickstarts-listed-win8.png! > Application wizard: Can not show quickstarts list > ------------------------------------------------- > > Key: JBIDE-18696 > URL: https://issues.jboss.org/browse/JBIDE-18696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Windows 8 + Eclipse Luna (4.4) > Reporter: Chunyun Chen > Attachments: quickstarts-listed-win8.png, Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log > > > The quickstarts are unable to be shown, so any quickstarts can not be chosen to create. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18696: ------------------------------------- Attachment: quickstarts-listed-win8.png > Application wizard: Can not show quickstarts list > ------------------------------------------------- > > Key: JBIDE-18696 > URL: https://issues.jboss.org/browse/JBIDE-18696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Windows 8 + Eclipse Luna (4.4) > Reporter: Chunyun Chen > Attachments: quickstarts-listed-win8.png, Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log > > > The quickstarts are unable to be shown, so any quickstarts can not be chosen to create. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-18696 at 10/27/14 7:24 AM: -------------------------------------------------------------------- I tried to replicate this using win8 and the exact same devenv (ec2-54-91-37-89.compute-1.amazonaws.com). I couldnt, I got the quickstarts right ahead: # ASSERT: make sure you have "-Djsse.enableSNIExtension=false" in your eclipse.ini (or jbdevstudio.ini) # EXEC: launch JBDS/Eclipse # EXEC: File->New->OpenShift->New Application # EXEC: New Connection, point it to ec2-54-91-37-89.compute-1.amazonaws.com and use some random credentials # EXEC: Look at the quickstart cathegory Result: It's fully popullated with entries (for me) !quickstarts-listed-win8.png! was (Author: adietish): I tried to replicate this using win8 and the exact same devenv (ec2-54-91-37-89.compute-1.amazonaws.com). I couldnt, I got the quickstarts right ahead: # ASSERT: make sure you have "-Djsse.enableSNIExtension=false" in your eclipse.ini (or jbdevstudio.ini) # EXEC: File->New->OpenShift->New Application # EXEC: New Connection, point it to ec2-54-91-37-89.compute-1.amazonaws.com and use some random credentials # EXEC: Look at the quickstart cathegory Result: It's fully popullated with entries (for me) !quickstarts-listed-win8.png! > Application wizard: Can not show quickstarts list > ------------------------------------------------- > > Key: JBIDE-18696 > URL: https://issues.jboss.org/browse/JBIDE-18696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Windows 8 + Eclipse Luna (4.4) > Reporter: Chunyun Chen > Attachments: quickstarts-listed-win8.png, Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log > > > The quickstarts are unable to be shown, so any quickstarts can not be chosen to create. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-18696: ------------------------------------------ I tried to replicate this using win8 and the exact same devenv (ec2-54-91-37-89.compute-1.amazonaws.com). I couldnt, I got the quickstarts right ahead: # ASSERT: make sure you have "-Djsse.enableSNIExtension=false" in your eclipse.ini (or jbdevstudio.ini) # EXEC: File->New->OpenShift->New Application # EXEC: New Connection, point it to ec2-54-91-37-89.compute-1.amazonaws.com and use some random credentials # EXEC: Look at the quickstart cathegory Result: It's fully popullated with entries (for me) !quickstarts-listed-win8.png! > Application wizard: Can not show quickstarts list > ------------------------------------------------- > > Key: JBIDE-18696 > URL: https://issues.jboss.org/browse/JBIDE-18696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Windows 8 + Eclipse Luna (4.4) > Reporter: Chunyun Chen > Attachments: Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log > > > The quickstarts are unable to be shown, so any quickstarts can not be chosen to create. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17212) Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17212?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17212: ------------------------------------- [~mmalina] Please verify steps to replicate here > Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-17212 > URL: https://issues.jboss.org/browse/JBIDE-17212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.x > > > As you said in JBIDE-7515, when you specify startup and shutdown scripts with a deploy-only server, the server process should be killed if the shutdown script fails. But that is not the case. > From JBIDE-7515: > {quote} > I left the shutdown script empty. > You said that if the shutdown script fails, the process ID will be killed. Maybe technically an empty command does not fail, but I believe in this case the running java process should still be killed and it isn't. > In fact, it doesn't work even if I put something that will fail there, e.g. "exit 1". > {quote} > The shutdown should default to process kill even if the shutdown script is empty. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17618) Server start button disabled after Eclipse restart

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17618?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17618: ------------------------------------- I can't replicate this [~mmalina] Is this still an issue for you? > Server start button disabled after Eclipse restart > -------------------------------------------------- > > Key: JBIDE-17618 > URL: https://issues.jboss.org/browse/JBIDE-17618 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.x > > Attachments: disabled-server-start.png > > > When you restart Eclipse with the Server View open, right after the IDE start, the first server will be selected, but the Start button cannot be clicked. > !disabled-server-start.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18461) org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18461?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18461: ------------------------------------- I've closed the clone, because as far as I can tell, there won't be a 4.1.3. Sorry. > org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61 > -------------------------------------------------------------------------------- > > Key: JBIDE-18461 > URL: https://issues.jboss.org/browse/JBIDE-18461 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Brian Fitzpatrick > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.CR2 > > > When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18523) [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18523?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-18523. --------------------------------- Fix Version/s: (was: 4.1.2.Final) Resolution: Rejected 4.1.2 was like 9 months ago. There is no 4.1.3 planned. Sorry. > [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61 > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18523 > URL: https://issues.jboss.org/browse/JBIDE-18523 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > > When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15189) Check compatible JRE/JDK when adding server via runtime detection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15189?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-15189: ----------------------------------- Assignee: Rob Stryker > Check compatible JRE/JDK when adding server via runtime detection > ----------------------------------------------------------------- > > Key: JBIDE-15189 > URL: https://issues.jboss.org/browse/JBIDE-15189 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.1.0.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.1.x, 4.2.x > > > Now, people are not allowed to create runtime when no compatible java is configured in eclipse (JBIDE-14858). > But when adding server and runtime via runtime detection, server and runtime are added even though no compatible java is configured. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18554) JPP 6.1 is in "started" state before it is completely started.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18554?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-18554. --------------------------------- Assignee: Rob Stryker Fix Version/s: 4.2.0.Final Resolution: Rejected I've tested the following workarounds: 1) Open server editor, change pollers to mgmt poller or 2) Open server editor, click on behavior profile, switch to local and "prefers mgmt operations" Both of these work as expected. If you want a server that uses mgmt operations in all places, you should modify the behavior profile as done in step 2). This would include performing deployments over management. If on the other hand you just want to use the management poller, you should perform as step 1) indicates, and only modify the server state detectors / pollers to use management. As far as I'm concerned, the server is behaving appropriately. We should not be using management pollers if the user created it in the local + filesystem operation profile. The web port poller has its limitations but is functioning as expected here. The management poller works as expected here as well. > JPP 6.1 is in "started" state before it is completely started. > -------------------------------------------------------------- > > Key: JBIDE-18554 > URL: https://issues.jboss.org/browse/JBIDE-18554 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR2 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.2.0.Final > > > When starting JPP 6.1 (I haven't tried it with other versions yet), the server is in "Started" state in servers view before it is completely started. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2014