[JBoss JIRA] (JBIDE-25602) NullPointerException in RegistryProviderModel.getRegistryURL
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25602?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25602:
-------------------------------------
Fix Version/s: 4.5.x
> NullPointerException in RegistryProviderModel.getRegistryURL
> ------------------------------------------------------------
>
> Key: JBIDE-25602
> URL: https://issues.jboss.org/browse/JBIDE-25602
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Automated Error Reporting Bot
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.openshift.core.connection.registry.RegistryProviderModel.getRegistryURL(RegistryProviderModel.java:37)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor.discoverRegistryPressed(AdvancedConnectionEditor.java:302)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor.access$2(AdvancedConnectionEditor.java:300)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor$1$1.widgetSelected(AdvancedConnectionEditor.java:128)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> {noformat}
> Bundles:
> | org.eclipse.swt | 3.106.0.v20170608-0516 | 3.106.1.v20170926-0519 |
> | org.jboss.tools.openshift.core | 3.4.1.v20171025-1008 | 3.4.2.v20171115-1821 |
> | org.jboss.tools.openshift.ui | 3.4.1.v20171025-1219 | 3.4.2.v20171115-1650 |
> Operating Systems:
> | Linux | 4.10.0 | 4.10.0 |
> | MacOSX | 10.13.1 | 10.13.2 |
> | Windows | 6.2.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://aer.ctrlflow.com/redhat/reviewers/#!/problems/5a2a4339e4b037...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25602) NullPointerException in RegistryProviderModel.getRegistryURL
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25602?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25602:
-------------------------------------
Priority: Minor (was: Major)
> NullPointerException in RegistryProviderModel.getRegistryURL
> ------------------------------------------------------------
>
> Key: JBIDE-25602
> URL: https://issues.jboss.org/browse/JBIDE-25602
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Automated Error Reporting Bot
> Priority: Minor
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.openshift.core.connection.registry.RegistryProviderModel.getRegistryURL(RegistryProviderModel.java:37)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor.discoverRegistryPressed(AdvancedConnectionEditor.java:302)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor.access$2(AdvancedConnectionEditor.java:300)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor$1$1.widgetSelected(AdvancedConnectionEditor.java:128)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> {noformat}
> Bundles:
> | org.eclipse.swt | 3.106.0.v20170608-0516 | 3.106.1.v20170926-0519 |
> | org.jboss.tools.openshift.core | 3.4.1.v20171025-1008 | 3.4.2.v20171115-1821 |
> | org.jboss.tools.openshift.ui | 3.4.1.v20171025-1219 | 3.4.2.v20171115-1650 |
> Operating Systems:
> | Linux | 4.10.0 | 4.10.0 |
> | MacOSX | 10.13.1 | 10.13.2 |
> | Windows | 6.2.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://aer.ctrlflow.com/redhat/reviewers/#!/problems/5a2a4339e4b037...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBDS-4664) Update copyright year in DevStudio
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBDS-4664?page=com.atlassian.jira.plugin.... ]
Ondrej Dockal edited comment on JBDS-4664 at 1/20/18 6:40 AM:
--------------------------------------------------------------
Thought so, thanks!
was (Author: odockal):
Though so, thanks!
> Update copyright year in DevStudio
> ----------------------------------
>
> Key: JBDS-4664
> URL: https://issues.jboss.org/browse/JBDS-4664
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: legal, ui/branding
> Affects Versions: 11.2.0.AM3
> Environment: Red Hat JBoss Developer Studio
> Version: 11.2.0.AM3
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
> Fix For: 11.3.0.AM1
>
> Attachments: splash.bmp
>
>
> Update copyright year on splash screen and in about dialog of devstudio to 2018(it is now 2017).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBDS-4664) Update copyright year in DevStudio
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4664?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4664:
----------------------------------
Too late to fix for 11.2, and nonblocking. Slip to 11.3.
> Update copyright year in DevStudio
> ----------------------------------
>
> Key: JBDS-4664
> URL: https://issues.jboss.org/browse/JBDS-4664
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: legal, ui/branding
> Affects Versions: 11.2.0.AM3
> Environment: Red Hat JBoss Developer Studio
> Version: 11.2.0.AM3
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
> Fix For: 11.3.0.AM1
>
> Attachments: splash.bmp
>
>
> Update copyright year on splash screen and in about dialog of devstudio to 2018(it is now 2017).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (ERT-593) C# debugging
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/ERT-593?page=com.atlassian.jira.plugin.sy... ]
Mickael Istria updated ERT-593:
-------------------------------
Description:
This ticket tracks long-term progress, investigation and possible actions about C# debugging on Eclipse IDE (or other non VS/VSCode IDEs).
Current state is the vsdbg, which has support for debug adapter protocol (so it would be easy to consume in Eclipse IDE/Che) actually has a vendor lock which prevents it to start when not invoked from VS or VSCode.
An alternative can be to follow https://github.com/Samsung/netcoredbg/issues/1 and use this debugger in place of vsdbg as soon as debug adapter protocol support is in.
If we want to experiment another alternative that may work now, we can also try to write a VSCode extension that would start the vsdbg and simply forward streams. So the client (Eclipse IDE, Eclipse Che) could just create sockets and start `vscode` with some options (such environment variables) to have VSCode start vsdbg and connecting to the parameterized socket. Hopefully, as it would be VSCode invoking vsdbg, vsdbg would work and the extension would make vscode proxy would be a good server adapter for clients.
was:
This ticket tracks long-term progress, investigation and possible actions about C# debugging on Eclipse IDE (or other non VS/VSCode IDEs).
Current state is the vsdbg, which has support for debug adapter protocol (so it would be easy to consume in Eclipse IDE/Che) actually has a vendor lock which prevents it to start when not invoked from VS or VSCode.
An alternative can be to follow https://github.com/Samsung/netcoredbg/issues/1 and use this debugger in place of vsdbg as soon as debug adapter protocol support is in.
If we want to experiment, we can also try to write a VSCode extension that would start the vsdbg and simply forward streams. So the client (Eclipse IDE, Eclipse Che) could just create sockets and start `vscode` with some options (such environment variables) to have VSCode start vsdbg and connecting to the parameterized socket. Hopefully, as it would be VSCode invoking vsdbg, vsdbg would work and the extension would make vscode proxy would be a good server adapter for clients.
> C# debugging
> ------------
>
> Key: ERT-593
> URL: https://issues.jboss.org/browse/ERT-593
> Project: Eclipse Release Train
> Issue Type: Enhancement
> Reporter: Mickael Istria
>
> This ticket tracks long-term progress, investigation and possible actions about C# debugging on Eclipse IDE (or other non VS/VSCode IDEs).
> Current state is the vsdbg, which has support for debug adapter protocol (so it would be easy to consume in Eclipse IDE/Che) actually has a vendor lock which prevents it to start when not invoked from VS or VSCode.
> An alternative can be to follow https://github.com/Samsung/netcoredbg/issues/1 and use this debugger in place of vsdbg as soon as debug adapter protocol support is in.
> If we want to experiment another alternative that may work now, we can also try to write a VSCode extension that would start the vsdbg and simply forward streams. So the client (Eclipse IDE, Eclipse Che) could just create sockets and start `vscode` with some options (such environment variables) to have VSCode start vsdbg and connecting to the parameterized socket. Hopefully, as it would be VSCode invoking vsdbg, vsdbg would work and the extension would make vscode proxy would be a good server adapter for clients.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (ERT-593) C# debugging
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/ERT-593?page=com.atlassian.jira.plugin.sy... ]
Mickael Istria updated ERT-593:
-------------------------------
Description:
This ticket tracks long-term progress, investigation and possible actions about C# debugging on Eclipse IDE (or other non VS/VSCode IDEs).
Current state is the vsdbg, which has support for debug adapter protocol (so it would be easy to consume in Eclipse IDE/Che) actually has a vendor lock which prevents it to start when not invoked from VS or VSCode.
An alternative can be to follow https://github.com/Samsung/netcoredbg/issues/1 and use this debugger in place of vsdbg as soon as debug adapter protocol support is in.
If we want to experiment, we can also try to write a VSCode extension that would start the vsdbg and simply forward streams. So the client (Eclipse IDE, Eclipse Che) could just create sockets and start `vscode` with some options (such environment variables) to have VSCode start vsdbg and connecting to the parameterized socket. Hopefully, as it would be VSCode invoking vsdbg, vsdbg would work and the extension would make vscode proxy would be a good server adapter for clients.
was:
This ticket tracks long-term progress, investigation and possible actions about C# debugging on Eclipse IDE (or other non VS/VSCode IDEs).
Current state is the vsdbg, which has support for debug adapter protocol -so it would be easy to consume in Eclipse IDE/Che- actually has a vendor lock which prevents it to start when not invoked from VS or VSCode.
An alternative can be to follow https://github.com/Samsung/netcoredbg/issues/1 and use this debugger in place of vsdbg as soon as debug adapter protocol support is in.
If we want to experiment, we can also try to write a VSCode extension that would start the vsdbg and simply forward streams. So the client (Eclipse IDE, Eclipse Che) could just create sockets and start `vscode` with some options (such environment variables) to have VSCode start vsdbg and connecting to the parameterized socket. Hopefully, as it would be VSCode invoking vsdbg, vsdbg would work and the extension would make vscode proxy would be a good server adapter for clients.
> C# debugging
> ------------
>
> Key: ERT-593
> URL: https://issues.jboss.org/browse/ERT-593
> Project: Eclipse Release Train
> Issue Type: Enhancement
> Reporter: Mickael Istria
>
> This ticket tracks long-term progress, investigation and possible actions about C# debugging on Eclipse IDE (or other non VS/VSCode IDEs).
> Current state is the vsdbg, which has support for debug adapter protocol (so it would be easy to consume in Eclipse IDE/Che) actually has a vendor lock which prevents it to start when not invoked from VS or VSCode.
> An alternative can be to follow https://github.com/Samsung/netcoredbg/issues/1 and use this debugger in place of vsdbg as soon as debug adapter protocol support is in.
> If we want to experiment, we can also try to write a VSCode extension that would start the vsdbg and simply forward streams. So the client (Eclipse IDE, Eclipse Che) could just create sockets and start `vscode` with some options (such environment variables) to have VSCode start vsdbg and connecting to the parameterized socket. Hopefully, as it would be VSCode invoking vsdbg, vsdbg would work and the extension would make vscode proxy would be a good server adapter for clients.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (ERT-593) C# debugging
by Mickael Istria (JIRA)
Mickael Istria created ERT-593:
----------------------------------
Summary: C# debugging
Key: ERT-593
URL: https://issues.jboss.org/browse/ERT-593
Project: Eclipse Release Train
Issue Type: Enhancement
Reporter: Mickael Istria
This ticket tracks long-term progress, investigation and possible actions about C# debugging on Eclipse IDE (or other non VS/VSCode IDEs).
Current state is the vsdbg, which has support for debug adapter protocol -so it would be easy to consume in Eclipse IDE/Che- actually has a vendor lock which prevents it to start when not invoked from VS or VSCode.
An alternative can be to follow https://github.com/Samsung/netcoredbg/issues/1 and use this debugger in place of vsdbg as soon as debug adapter protocol support is in.
If we want to experiment, we can also try to write a VSCode extension that would start the vsdbg and simply forward streams. So the client (Eclipse IDE, Eclipse Che) could just create sockets and start `vscode` with some options (such environment variables) to have VSCode start vsdbg and connecting to the parameterized socket. Hopefully, as it would be VSCode invoking vsdbg, vsdbg would work and the extension would make vscode proxy would be a good server adapter for clients.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months