December 2018 - jbosstools-issues

[JBoss JIRA] (JBDS-4743) When saving an xhtml file, getting JSF error popup

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4743?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4743: ---------------------------------- [checkUnresolvedIssues.py] Slip to fixversion = *12.x* > When saving an xhtml file, getting JSF error popup > -------------------------------------------------- > > Key: JBDS-4743 > URL: https://issues.jboss.org/browse/JBDS-4743 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: jsf > Affects Versions: 12.9.0.GA > Environment: JBDS 12.9 on macOS mojave > Reporter: Fabi Yo > Assignee: Jeff MAURY > Priority: Major > Fix For: 12.x > > Attachments: Schermafbeelding 2018-11-07 om 9.42.32 AM.png, fieldWizard.xhtml, log.txt, web.xml > > > I am working on an xhtml file which contains JSF tags. I can work normally in it. After a while (random) when I save an xhtml file, I get this popup saying: > 'Refreshing JSF information about: ..... ' > An internal error occured. > The problem is, from the moment i get it, it doesn't stop. After a while it gets very annoying. > I wish I could tell you more, but the error popup is quite vague... > See more info in the picture in attachment -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4742) Ensure devstudio can be installed w/ JDK 11 or 12-ea

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4742?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4742: ----------------------------- Fix Version/s: 12.x (was: 12.10.0.AM1) > Ensure devstudio can be installed w/ JDK 11 or 12-ea > ---------------------------------------------------- > > Key: JBDS-4742 > URL: https://issues.jboss.org/browse/JBDS-4742 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Major > Fix For: 12.x > > > Now that JDK 11 is the LTS standard, replacing 8, the installer should be updated so it works with 11, and 12-ea too. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26406) Update server integration tests to include EAP 7.2 Beta

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26406?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26406: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.11.x* > Update server integration tests to include EAP 7.2 Beta > ------------------------------------------------------- > > Key: JBIDE-26406 > URL: https://issues.jboss.org/browse/JBIDE-26406 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.9.0.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Major > Labels: EAP, EAP_7, server > Fix For: 4.11.x > > > EAP 7.2 Beta is out since August 26th. We should update the server integration tests so that EAP QE can use our integration tests against it -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26330) Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26330?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26330: ------------------------------- Fix Version/s: 4.11.x (was: 4.10.0.AM1) > Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26330 > URL: https://issues.jboss.org/browse/JBIDE-26330 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Major > Fix For: 4.11.x > > > steps: > # EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... > # EXEC: import the "hello" maven project into your Eclipse > # EXEC: create a server adapter and start it > # ASSERT: server adapter for project "hello" is *[Started, Synchronized]* > # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... > # ASSERT: *"openshift"* maven profile is selected > # EXEC: Restart Eclipse > # ASSERT: server adapter for project "hello" is *[Stopped, Republish]* > # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... > Result: > Project "hello" still has *"openshift"* profile selected > Expected result: > Project "hello" still has *no profile* selected (starting the server adapter selects the "openshift" profile, while stopping it unselects it.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26330) Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26330?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26330: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.11.x* > Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26330 > URL: https://issues.jboss.org/browse/JBIDE-26330 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Major > Fix For: 4.11.x > > > steps: > # EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... > # EXEC: import the "hello" maven project into your Eclipse > # EXEC: create a server adapter and start it > # ASSERT: server adapter for project "hello" is *[Started, Synchronized]* > # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... > # ASSERT: *"openshift"* maven profile is selected > # EXEC: Restart Eclipse > # ASSERT: server adapter for project "hello" is *[Stopped, Republish]* > # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... > Result: > Project "hello" still has *"openshift"* profile selected > Expected result: > Project "hello" still has *no profile* selected (starting the server adapter selects the "openshift" profile, while stopping it unselects it.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26311) EAP 7.1 fails to stop when connected over ssh

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26311?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26311: ------------------------------- Fix Version/s: 4.11.x (was: 4.10.0.AM1) > EAP 7.1 fails to stop when connected over ssh > --------------------------------------------- > > Key: JBIDE-26311 > URL: https://issues.jboss.org/browse/JBIDE-26311 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.9.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Major > Labels: regression > Fix For: 4.11.x > > Attachments: JBIDE-26311.local.ogv > > > I have an EAP 7.1 setup up over ssh. It's running on my localhost, so it's the most basic test of an ssh server. When I click the stop button on the server, it says: > Server Red Hat JBoss EAP 7.1 ssh failed to stop. > An exception stack trace is not available. > It will stop on second attempt. On a local server this would mean killing the server java process. I'm not sure exactly what happens on a remote server, but it works. > I'm pretty sure this worked last time (previous milestone). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26311) EAP 7.1 fails to stop when connected over ssh

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26311?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26311: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.11.x* > EAP 7.1 fails to stop when connected over ssh > --------------------------------------------- > > Key: JBIDE-26311 > URL: https://issues.jboss.org/browse/JBIDE-26311 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.9.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Major > Labels: regression > Fix For: 4.11.x > > Attachments: JBIDE-26311.local.ogv > > > I have an EAP 7.1 setup up over ssh. It's running on my localhost, so it's the most basic test of an ssh server. When I click the stop button on the server, it says: > Server Red Hat JBoss EAP 7.1 ssh failed to stop. > An exception stack trace is not available. > It will stop on second attempt. On a local server this would mean killing the server java process. I'm not sure exactly what happens on a remote server, but it works. > I'm pretty sure this worked last time (previous milestone). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26255) Cannot OpenOn existing xhtml web page in faces-config.xml

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26255?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26255: ------------------------------- Fix Version/s: 4.11.x (was: 4.10.0.AM1) > Cannot OpenOn existing xhtml web page in faces-config.xml > --------------------------------------------------------- > > Key: JBIDE-26255 > URL: https://issues.jboss.org/browse/JBIDE-26255 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.9.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.x > > Attachments: openon-faces-config.gif > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26255) Cannot OpenOn existing xhtml web page in faces-config.xml

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26255?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26255: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.11.x* > Cannot OpenOn existing xhtml web page in faces-config.xml > --------------------------------------------------------- > > Key: JBIDE-26255 > URL: https://issues.jboss.org/browse/JBIDE-26255 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.9.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.x > > Attachments: openon-faces-config.gif > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26160: ------------------------------- Fix Version/s: 4.11.x (was: 4.10.0.AM1) > Server Adapter: erroneously stays in [Debugging] when you kill the pod > ---------------------------------------------------------------------- > > Key: JBIDE-26160 > URL: https://issues.jboss.org/browse/JBIDE-26160 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Major > Labels: server_adapter > Fix For: 4.11.x > > > steps: > # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it > # ASSERT: server adapter is created > # EXEC: start the server adapter in Debugging > # ASSERT: sever adapter is in *[Debugging, Synchronized]* state > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started > # EXEC: in Explorer: select the pod for your service and pick "Delete" > # ASSERT: pod gets deleted and recreated > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped > Result: > The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. Debugging doesn't work any more because the port forwarding was stopped. To have it running again you need to restart the port forwarding for the new pod. > Expected result: > Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 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 December 2018