[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 updated JBDS-4743:
-----------------------------
Fix Version/s: 12.x
(was: 12.10.0.AM1)
> 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)
5 years, 9 months
[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)
5 years, 9 months
[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)
5 years, 9 months
[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)
5 years, 9 months
[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)
5 years, 9 months
[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)
5 years, 9 months