November 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25442) Add possibility to be notified when user logs in into OSIO

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25442?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-25442: ---------------------------------------- Assignee: Jeff MAURY > Add possibility to be notified when user logs in into OSIO > ---------------------------------------------------------- > > Key: JBIDE-25442 > URL: https://issues.jboss.org/browse/JBIDE-25442 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.2.AM1 > Reporter: Lucia Jelinkova > Assignee: Jeff MAURY > Labels: OSIO > Fix For: 4.5.x > > > I have the following scenario I'd like to implement with OSIO login. I am not sure if it is currently possible or it would need some additional implementation. > The Fabric8 analytics plugin for Eclipse uses LSP server that needs OSIO token to work. The current implementation asks user for the token on the first open of pom.xml file and then every time the LSP server needs to be started (meaning on every open of any pom.xml file). This approach brings some disadvantages - e.g. user might cancel the login window and then he has manually re-enable the server on Fabric8 preference page. Not to mention that the login window out of the nowhere is quite disturbing. > I would like to change it so that the user logs in into OSIO (via toolbutton or preference page) and then the LSP server is notified about the login and starts working. This would prevent the "login popup" problem and I think it would bring better user experience. > So, is there a way to get notifications about login/logout into OSIO at the moment? Would you agree to implement this feature into OSIO Eclipse plugin? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25442) Add possibility to be notified when user logs in into OSIO

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25442?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25442: ------------------------------------- Fix Version/s: 4.5.x > Add possibility to be notified when user logs in into OSIO > ---------------------------------------------------------- > > Key: JBIDE-25442 > URL: https://issues.jboss.org/browse/JBIDE-25442 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.2.AM1 > Reporter: Lucia Jelinkova > Assignee: Jeff MAURY > Labels: OSIO > Fix For: 4.5.x > > > I have the following scenario I'd like to implement with OSIO login. I am not sure if it is currently possible or it would need some additional implementation. > The Fabric8 analytics plugin for Eclipse uses LSP server that needs OSIO token to work. The current implementation asks user for the token on the first open of pom.xml file and then every time the LSP server needs to be started (meaning on every open of any pom.xml file). This approach brings some disadvantages - e.g. user might cancel the login window and then he has manually re-enable the server on Fabric8 preference page. Not to mention that the login window out of the nowhere is quite disturbing. > I would like to change it so that the user logs in into OSIO (via toolbutton or preference page) and then the LSP server is notified about the login and starts working. This would prevent the "login popup" problem and I think it would bring better user experience. > So, is there a way to get notifications about login/logout into OSIO at the moment? Would you agree to implement this feature into OSIO Eclipse plugin? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25442) Add possibility to be notified when user logs in into OSIO

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25442?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25442: ------------------------------------- Affects Version/s: 4.5.2.AM1 > Add possibility to be notified when user logs in into OSIO > ---------------------------------------------------------- > > Key: JBIDE-25442 > URL: https://issues.jboss.org/browse/JBIDE-25442 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.2.AM1 > Reporter: Lucia Jelinkova > Assignee: Jeff MAURY > Labels: OSIO > Fix For: 4.5.x > > > I have the following scenario I'd like to implement with OSIO login. I am not sure if it is currently possible or it would need some additional implementation. > The Fabric8 analytics plugin for Eclipse uses LSP server that needs OSIO token to work. The current implementation asks user for the token on the first open of pom.xml file and then every time the LSP server needs to be started (meaning on every open of any pom.xml file). This approach brings some disadvantages - e.g. user might cancel the login window and then he has manually re-enable the server on Fabric8 preference page. Not to mention that the login window out of the nowhere is quite disturbing. > I would like to change it so that the user logs in into OSIO (via toolbutton or preference page) and then the LSP server is notified about the login and starts working. This would prevent the "login popup" problem and I think it would bring better user experience. > So, is there a way to get notifications about login/logout into OSIO at the moment? Would you agree to implement this feature into OSIO Eclipse plugin? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24961) New Application Wizard: include "Import Project" and "Server adapter creation" into the wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24961?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24961: ------------------------------------- Fix Version/s: 4.5.2.AM2 (was: 4.5.x) > New Application Wizard: include "Import Project" and "Server adapter creation" into the wizard > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24961 > URL: https://issues.jboss.org/browse/JBIDE-24961 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Fix For: 4.5.2.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24797) Code formatter: define and hook code formatting enforcement for github PRs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24797: ------------------------------------- Fix Version/s: 4.5.2.AM2 (was: 4.5.x) > Code formatter: define and hook code formatting enforcement for github PRs > -------------------------------------------------------------------------- > > Key: JBIDE-24797 > URL: https://issues.jboss.org/browse/JBIDE-24797 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: devdoc, hibernate, openshift, server > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.2.AM2 > > > Code formatting differs across developers. We should be at least consistent since odd formatting makes reading code more difficult for obvious reasons. > The most prominent differences I am aware of are > * use spaces vs tabs > * differences in formatting "if statements" (as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1536/files#d...]): > {code} > if(XX){ > {code} > vs > {code} > if (XX) { > {code} > * insonsitent code identations like displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...]: > {code} > public void method() { > int i = 0; > i++; > i +=2; > {code} > * odd identations of whole anonymous classes as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1531/files#d...] > {code} > class Listener { > int i = 0; > public void method() { > } > } > {code} > * multiple empty lines for no obvious reason like shown [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...] > {code} > public class ZZ { > int i = 0; > i++ > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24845) [regression] unable to open the Maven Repositories wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24845?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24845: ------------------------------------- Fix Version/s: 4.5.2.AM2 (was: 4.5.x) > [regression] unable to open the Maven Repositories wizard > --------------------------------------------------------- > > Key: JBIDE-24845 > URL: https://issues.jboss.org/browse/JBIDE-24845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.4.4.Final > Reporter: Fred Bricon > Assignee: Dmitrii Bocharov > Fix For: 4.5.2.AM2 > > > 1 - open Preferences > JBoss Tools > JBoss Maven Integration > 2 - click on the Configure Maven Repositories... button > expected: the Maven repositories wizard open > actual: Unhandled event loop exception: > {noformat} > java.lang.NoSuchFieldError: DEFAULT_USER_SETTINGS_FILE > at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.getUserSettings(ConfigureMavenRepositoriesWizardPage.java:988) > at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.createControl(ConfigureMavenRepositoriesWizardPage.java:242) > at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:176) > at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:688) > at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:580) > at org.eclipse.jface.window.Window.create(Window.java:426) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096) > at org.jboss.tools.maven.ui.preferences.ConfiguratorPreferencePage$2.widgetSelected(ConfiguratorPreferencePage.java:155) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4257) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1502) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1525) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1510) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1314) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4081) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) > at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:59) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25444) Declare JAVA17 - JAVA19 ENV vars on mac slaves

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25444?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25444: ------------------------------------ Per [~psrna], we should NOT use the Tool environment injection workaround. Running experiments to see which JDKs are found/resolved on 5 OSX slaves here (not using Tool env injections): https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/cci-expe... > Declare JAVA17 - JAVA19 ENV vars on mac slaves > ---------------------------------------------- > > Key: JBIDE-25444 > URL: https://issues.jboss.org/browse/JBIDE-25444 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, qa > Affects Versions: 4.5.1.Final > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.2.AM2 > > > JAVAxx env vars need to be declared on mac slaves: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/label/mac/ > For win and linux, it's set up here: > https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... > https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... > On mac slaves, we just need to add these to .bash_profile . Or maybe more than that because .bash_profile may not get called when jenkins slave starts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25444) Declare JAVAxx ENV vars on mac slaves

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25444?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-25444: ---------------------------------- Description: JAVAxx env vars need to be declared on mac slaves: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/label/mac/ For win and linux, it's set up here: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... On mac slaves, we just need to add these to .bash_profile . Or maybe more than that because .bash_profile may not get called when jenkins slave starts. was: JAVA19 env vars need to be declared on OSX boxes, as they were for windows and rhel CCI slaves (via JBIDE-25285). We should NOT use the Tool environment injection workaround. Running experiments to see which JDKs are found/resolved on 5 OSX slaves here: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/cci-expe... > Declare JAVAxx ENV vars on mac slaves > ------------------------------------- > > Key: JBIDE-25444 > URL: https://issues.jboss.org/browse/JBIDE-25444 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, qa > Affects Versions: 4.5.1.Final > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.2.AM2 > > > JAVAxx env vars need to be declared on mac slaves: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/label/mac/ > For win and linux, it's set up here: > https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... > https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... > On mac slaves, we just need to add these to .bash_profile . Or maybe more than that because .bash_profile may not get called when jenkins slave starts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25444) Declare JAVA17 - JAVA19 ENV vars on mac slaves

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25444?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25444: ------------------------------- Summary: Declare JAVA17 - JAVA19 ENV vars on mac slaves (was: Declare JAVAxx ENV vars on mac slaves) > Declare JAVA17 - JAVA19 ENV vars on mac slaves > ---------------------------------------------- > > Key: JBIDE-25444 > URL: https://issues.jboss.org/browse/JBIDE-25444 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, qa > Affects Versions: 4.5.1.Final > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.2.AM2 > > > JAVAxx env vars need to be declared on mac slaves: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/label/mac/ > For win and linux, it's set up here: > https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... > https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... > On mac slaves, we just need to add these to .bash_profile . Or maybe more than that because .bash_profile may not get called when jenkins slave starts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25444) Declare JAVAxx ENV vars on mac slaves

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25444?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25444: ------------------------------- Description: JAVA19 env vars need to be declared on OSX boxes, as they were for windows and rhel CCI slaves (via JBIDE-25285). We should NOT use the Tool environment injection workaround. Running experiments to see which JDKs are found/resolved on 5 OSX slaves here: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/cci-expe... was: JAVA19 env vars need to be declared on OSX boxes, as they were for windows and rhel CCI slaves (via JBIDE-25285). > Declare JAVAxx ENV vars on mac slaves > ------------------------------------- > > Key: JBIDE-25444 > URL: https://issues.jboss.org/browse/JBIDE-25444 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, qa > Affects Versions: 4.5.1.Final > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.2.AM2 > > > JAVA19 env vars need to be declared on OSX boxes, as they were for windows and rhel CCI slaves (via JBIDE-25285). We should NOT use the Tool environment injection workaround. > Running experiments to see which JDKs are found/resolved on 5 OSX slaves here: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/cci-expe... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 November 2017