[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:
-----------------------------
Sprint: devex #158 November 2018, devex #159 December 2018 (was: devex #158 November 2018)
> 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, 7 months
[JBoss JIRA] (JBIDE-24646) Import application: doesnt check if local branch match
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-24646?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24646:
-------------------------------
Sprint: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018)
> Import application: doesnt check if local branch match
> ------------------------------------------------------
>
> Key: JBIDE-24646
> URL: https://issues.jboss.org/browse/JBIDE-24646
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM1
> Reporter: Jan Novak
> Assignee: Dmitrii Bocharov
> Priority: Major
> Labels: import_app, openshift_v3
> Fix For: 4.11.x
>
>
> Importing project from Openshift
> * use existing repo
> * local repo uses different branch than Openshift
> * remote branch isnt locally fetched
> * import finishes succesfully
> * in local repo is *stil checkouted wrong branch*, without any warnings
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 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:
-------------------------------
Sprint: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018)
> 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, 7 months
[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:
-------------------------------
Sprint: devex #154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018 (was: devex #154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018)
> 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)
5 years, 7 months
[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25000:
-------------------------------
Sprint: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018 (was: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018)
> Server adapter: starting into debugging fails initially (succeeds on a latter try)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25000
> URL: https://issues.jboss.org/browse/JBIDE-25000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: openshift_v3, server_adapter
> Fix For: 4.11.x
>
> Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template
> # ASSERT: have a server adapter for it
> # EXEC/ASSERT: have the adapter started in non-debugging/normal mode
> # EXEC: restart the adapter debugging
> Result:
> !failed-to-connect-v8-vm.png!
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
> ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months