[JBoss JIRA] (JBIDE-26476) Launcher Application Wizard in the RHDS Central - exceptions appear when working with the UI (location and project name)
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26476?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka closed JBIDE-26476.
-----------------------------------
Issue is fixed, tested in Devstudio 12.11.0.AM1-v20190116-0732-B3834.
> Launcher Application Wizard in the RHDS Central - exceptions appear when working with the UI (location and project name)
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26476
> URL: https://issues.jboss.org/browse/JBIDE-26476
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.10.0.AM1
> Environment: OS X 10.13.6
> Reporter: Zbyněk Červinka
> Assignee: Josef Kopriva
> Priority: Major
> Fix For: 4.11.0.AM1
>
>
> There are an error in the Launcher Application Wizard in RHDS Central. When the "Use default location" checkbox in the Wizard is unchecked (=false) an then checked again, there appears the "An error occurred while setting the value." exception in the "Error log" view. Right after that, you can start writing the project name and with each keystroke the will appear more exceptions.
> NOTE: Sometimes there will appear "Server ‘org.eclipse.reddeer1’ failed with exception: null. ; version: 2.0.7.v20180504-0806" warning in the "Error log" view
> STACKTRACE 1:
> {code:java}
> eclipse.buildId=12.10.0.AM1-v20181023-0915-B3591
> java.version=1.8.0_181
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=cs_CZ
> Framework arguments: -product com.jboss.devstudio.core.product -keyring /Users/zcervink/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -keyring /Users/zcervink/.eclipse_keyring
> org.eclipse.core.databinding
> Error
> Thu Nov 29 16:42:38 CET 2018
> An error occurred while setting the value.
> java.lang.RuntimeException: java.lang.NullPointerException
> at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.writeProperty(BeanPropertyHelper.java:68)
> at org.eclipse.core.internal.databinding.beans.BeanValueProperty.doSetValue(BeanValueProperty.java:57)
> at org.eclipse.core.databinding.property.value.ValueProperty.setValue(ValueProperty.java:92)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.doSetValue(SimplePropertyObservableValue.java:103)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.setValue(AbstractObservableValue.java:69)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:113)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:113)
> at org.eclipse.core.databinding.UpdateValueStrategy.doSet(UpdateValueStrategy.java:476)
> at org.eclipse.core.databinding.ValueBinding.lambda$1(ValueBinding.java:200)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:152)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:156)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:174)
> at org.eclipse.core.databinding.ValueBinding.lambda$0(ValueBinding.java:193)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:152)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:156)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:174)
> at org.eclipse.core.databinding.ValueBinding.doUpdate(ValueBinding.java:162)
> at org.eclipse.core.databinding.ValueBinding.access$4(ValueBinding.java:151)
> at org.eclipse.core.databinding.ValueBinding$1.handleValueChange(ValueBinding.java:47)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:73)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:120)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:64)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:101)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.lambda$0(DecoratingObservableValue.java:76)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:73)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:120)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:85)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:119)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.lambda$1(SimplePropertyObservableValue.java:68)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:152)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:156)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:174)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.lambda$0(SimplePropertyObservableValue.java:66)
> at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:72)
> at org.eclipse.jface.internal.databinding.swt.WidgetListener.handleEvent(WidgetListener.java:59)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4292)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1512)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1535)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1520)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1324)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4116)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3733)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:821)
> at org.eclipse.jface.window.Window.open(Window.java:797)
> at org.jboss.tools.central.internal.WizardSupport.openWizard(WizardSupport.java:71)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$9.run(GettingStartedHtmlPage.java:431)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4068)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3735)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:628)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:199)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:391)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:246)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
> Caused by: java.lang.NullPointerException
> {code}
> STACKTRACE 2:
> {code:java}
> eclipse.buildId=12.10.0.AM1-v20181023-0915-B3591
> java.version=1.8.0_181
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=cs_CZ
> Framework arguments: -product com.jboss.devstudio.core.product -keyring /Users/zcervink/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -keyring /Users/zcervink/.eclipse_keyring
> org.eclipse.core.databinding
> Error
> Thu Nov 29 16:42:42 CET 2018
> Unhandled exception: java.lang.NullPointerException
> java.lang.RuntimeException: java.lang.NullPointerException
> at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.writeProperty(BeanPropertyHelper.java:68)
> at org.eclipse.core.internal.databinding.beans.BeanValueProperty.doSetValue(BeanValueProperty.java:57)
> at org.eclipse.core.databinding.property.value.ValueProperty.setValue(ValueProperty.java:92)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.doSetValue(SimplePropertyObservableValue.java:103)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.setValue(AbstractObservableValue.java:69)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:113)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:113)
> at org.eclipse.core.databinding.UpdateValueStrategy.doSet(UpdateValueStrategy.java:476)
> at org.eclipse.core.databinding.ValueBinding.lambda$1(ValueBinding.java:200)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:152)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:156)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:174)
> at org.eclipse.core.databinding.ValueBinding.lambda$0(ValueBinding.java:193)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:152)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:156)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:174)
> at org.eclipse.core.databinding.ValueBinding.doUpdate(ValueBinding.java:162)
> at org.eclipse.core.databinding.ValueBinding.access$4(ValueBinding.java:151)
> at org.eclipse.core.databinding.ValueBinding$1.handleValueChange(ValueBinding.java:47)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:73)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:120)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:64)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:101)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.lambda$0(DecoratingObservableValue.java:76)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:73)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:120)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:85)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:119)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.lambda$1(SimplePropertyObservableValue.java:68)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:152)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:156)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:174)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.lambda$0(SimplePropertyObservableValue.java:66)
> at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:72)
> at org.eclipse.jface.internal.databinding.swt.WidgetListener.handleEvent(WidgetListener.java:59)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4292)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1512)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1535)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1520)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1324)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4116)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3733)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:821)
> at org.eclipse.jface.window.Window.open(Window.java:797)
> at org.jboss.tools.central.internal.WizardSupport.openWizard(WizardSupport.java:71)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$9.run(GettingStartedHtmlPage.java:431)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4068)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3735)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:628)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:199)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:391)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:246)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
> Caused by: java.lang.NullPointerException
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (JBIDE-26503) Several Imported Launcher Application projects has some error in their files after importing
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26503?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26503:
-------------------------------
Sprint: devex #159 December 2018, devex #161 January 2019 (was: devex #159 December 2018)
> Several Imported Launcher Application projects has some error in their files after importing
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-26503
> URL: https://issues.jboss.org/browse/JBIDE-26503
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.10.0.AM1
> Environment: OS X 10.13.6
> Reporter: Zbyněk Červinka
> Assignee: Andre Dietisheim
> Priority: Major
> Fix For: 4.11.0.AM1
>
> Attachments: cache_vert.x_red hat_1.png, cache_vert.x_red hat_2.png
>
>
> Launcher application projects and their errors (description with settings):
> 1) Mission: "crud", Runtime: "thorntail community"
> 2) Mission: "crud", Runtime: "thorntail red hat"
> - 4 missing HTML </p> tags in file "src/licences/bouncy castle licence - licence.html" on line 50, 51, 52, 53
> 3) Mission: "crud", Runtime: "vert.x community"
> 4) Mission: "crud", Runtime: "vert.x red hat"
> - 3 errors in the project:
> a) Failure to transfer org.codehaus.mojo:buildnumber-maven-plugin:pom:1.4 from https://repository.jboss.org/nexus/content/groups/public-jboss/ was cached in the local repository, resolution will not be...
> b) The project was not built since its build path is incomplete. Cannot find the class file for java.lang.Object. Fix the build path then try building this project
> c) The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files
> 5) Mission: "cache", Runtime: "vert.x red hat"
> 6) Mission: "cache", Runtime: "vert.x community"
> - several errors during import and after import (2 images; also in the attachment):
> !cache_vert.x_red hat_2.png|thumbnail! !cache_vert.x_red hat_1.png|thumbnail!
> Maybe several other errors.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (JBDS-4735) Central projects Wizard sometimes fails to open
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBDS-4735?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4735:
-----------------------------
Sprint: devex #159 December 2018, devex #161 January 2019 (was: devex #159 December 2018)
> Central projects Wizard sometimes fails to open
> -----------------------------------------------
>
> Key: JBDS-4735
> URL: https://issues.jboss.org/browse/JBDS-4735
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 12.9.0.GA
> Environment: manually Fedora 28, automation
> Reporter: Vojtech Prusa
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 12.x
>
> Attachments: central.tar.gz, image-2018-10-17-09-24-31-555.png, screenshot-1.png
>
>
> Sometimes central examples wizards fail to load and modal dialog is shown instead (screen attached).
> Nothing in Error log view.
> Restarting devstudio solves the issue.
> Adding screen and central tar of:
> devstudio-12.9.0.GA-v20180928-1629-B3448/workspaces/workspace/.metadata/.plugins/org.jboss.tools.central/central
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (JBIDE-26117) Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26117?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26117:
-------------------------------
Sprint: devex #159 December 2018, devex #161 January 2019 (was: devex #159 December 2018)
> Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-26117
> URL: https://issues.jboss.org/browse/JBIDE-26117
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.Final
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Major
> Labels: connection_wizard
> Fix For: 4.11.0.AM1
>
>
> The OpenShift web-ui provides a menu entry that creates the oc login command in your local clipboard: https://stackoverflow.com/questions/49548380/cannot-find-openshift-3-logi...
> Currently, Eclipse users would have to paste it to some notepad and use the info in it to manually create a connection. The tooling could facilitate this by parsing the clipboard and creating a connection:
> The Eclipse
> There could be a button for parsing login command in clipboard.
> Steps:
> 1. User logins in web browser in OpenShift Console.
> 2. User clicks on "Copy Login Command"
> 3. In OpenShift tooling there could be button for parse login command from clipboard.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (JBIDE-26452) Explore existing proxy server set up solutions outside RH - proxy requirements definition
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26452?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26452:
-------------------------------
Sprint: devex #157 November 2019, devex #159 December 2018, devex #161 January 2019 (was: devex #157 November 2019, devex #159 December 2018)
> Explore existing proxy server set up solutions outside RH - proxy requirements definition
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-26452
> URL: https://issues.jboss.org/browse/JBIDE-26452
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.10.0.AM1
> Environment: Linux
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Major
> Labels: quality
> Fix For: 4.11.0.AM1
>
>
> Explore existing solutions for proxy configuration that could be done at one step without requiring deep user knowledge.
> Existing docker images with squid (other?) proxy. Licensing, usage within RH intranet. Is there an open source code?
> Requirements for proxy solution:
> * Supports HTTP and HTTPS protocols
> * Clear and configurable logging and other tools
> * runs on linux
> * Open Source solution
> * License usable "in house" (can be use for profit = in enterprise environment)
> * Project is alive/maintained - or we would must maintain our own fork?
> * Community
> * Code on github - preferably
> * uses issue tracking system
> Requirements for putting proxy into action:
> * easy to deploy solution
> * does not require user knowledge of proxy configuration - minimalist config
> * can be updated at place
> * RH certificate can be used
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (JBIDE-26453) Adapters/vscode-openshift tooling onboarding
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26453?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26453:
-------------------------------
Sprint: devex #157 November 2019, devex #159 December 2018, devex #161 January 2019 (was: devex #157 November 2019, devex #159 December 2018)
> Adapters/vscode-openshift tooling onboarding
> --------------------------------------------
>
> Key: JBIDE-26453
> URL: https://issues.jboss.org/browse/JBIDE-26453
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.10.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Labels: integration-test, quality
> Fix For: 4.11.0.AM1
>
>
> Jump in adapters stuff:
> * go through repos, get familiar with plugins
> * start exploring locally, build it, run it
> * pick up github issues and start implementing in typescript/java
> * increase unit tests coverage
> * get familiar with infrastructure
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months