September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4039) Installation of devsite fails when user name contains non-ascii character

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBDS-4039: ----------------------------------- Summary: Installation of devsite fails when user name contains non-ascii character Key: JBDS-4039 URL: https://issues.jboss.org/browse/JBDS-4039 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 1.1.0.GA Environment: Windows 7 Pro, x86_64, SP1 devsuite-1.1.0-GA-20160830-124-bundle-installer.exe Reporter: Ondrej Dockal Assignee: Denis Golovin Installation fails with Devstudio and VirtualBox error during installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3618) Progress does not reflect actual amount of work done

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3618?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3618. ----------------------------- Done. > Progress does not reflect actual amount of work done > ---------------------------------------------------- > > Key: JBDS-3618 > URL: https://issues.jboss.org/browse/JBDS-3618 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Jan Richter > Assignee: Jan Richter > Priority: Minor > Labels: havoc, ui > Fix For: 10.1.0.GA > > > It seems the current way the progress tracking is implemented is simply by giving an initial time estimate for each component. The progress bars then just count down the supplied time with no relation to the actual progress achieved. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3981: ----------------------------------- I'm still getting the same errors even after deleting the .eclipse folder. > Build a new feature that omits features available from RPM install > ------------------------------------------------------------------ > > Key: JBDS-3981 > URL: https://issues.jboss.org/browse/JBDS-3981 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.1.0.GA > > Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png > > > What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23054) Build for java-language-server

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23054?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-23054: -------------------------------------- Q: How often will this be published? A: Not often, and this is until VSCode marketplace can support larger download sizes Q :Do you have a preferred timestamp format? A: No, timestamp is just needed to produce unique URL for every unique release. These binaries will be downloaded by VSCode instances since we have no way of controlling the when those instances are updated on the field, we need to have multiple versions of the server distribution live. So we will tie a vscode extension version to a URL. Q: Should automated cleanup ever happen? A: No, Q: Is this stuff specific to a version of Eclipse? A: it is using neon at the moment Q: Do you plan to differentiate between /stable/ (GA) or /development/ (milestone) releases? What about snapshots (CI)? A: No > Build for java-language-server > ------------------------------ > > Key: JBIDE-23054 > URL: https://issues.jboss.org/browse/JBIDE-23054 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Gorkem Ercan > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > I need a build job that can build java-language server and publish it to download server for the use of VSCode extension. > Sources:_ https://github.com/gorkem/java-language-server_ > Build command: _mvn -Pserver-distro clean verify_ > Archive: server/org.jboss.tools.vscode.product/target/repository > Publish: file(s) under server/org.jboss.tools.vscode.product/distro/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23016: --------------------------------------- So it turns out that devsuite installer currently does not support installing for a regular user: JBDS-3841 {quote} To support "install for everybody" we would need to fix several issues related to how installer changes the environment and skip JBDS Start in the end to avoid creating configuration files for eclipse with administrative access rights. {quote} So this scenario would only apply if the user installs all the components manually, not using devsuite installer. But that's still a supported scenario I believe. And still believe it would actually work. > When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23016 > URL: https://issues.jboss.org/browse/JBIDE-23016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.1.Final > > > The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already). > This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights. > When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22738) Deploy docker wizard: Image registry URL becomes null when going between Connection and Deploy pages

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22738?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22738. --------------------------------- Verified in DevStudio 10.1.0.GA build ID GA-v20160901-0833-B5918. > Deploy docker wizard: Image registry URL becomes null when going between Connection and Deploy pages > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-22738 > URL: https://issues.jboss.org/browse/JBIDE-22738 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift > Affects Versions: 4.4.1.AM1 > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.AM3 > > Attachments: WAY1.webm, WAY2.webm > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3981: ---------------------------------- >From your [^.log] file I've concluded the following conflicting dependencies: {code} javax.annotation-api 1.2.0 (pulled in from org.glassfish.hk2.utils) and org.eclipse.osgi 3.11.0 both contribute package javax.annotation and both are singletons so can't have them both installed at the same time {code} And the following missing dependencies: {code} missing packages sun.security.util, com.sun.mail.util, com.sun.mail.smtp, com.sun.mail.auth missing plugin javax.mail.api {code} I wonder, if you re-ran eclipse using the -clean flag (and waited long enough for Eclipse to re-read all the dropins and droplets folders) would these errors still occur? What if you delete your ~/.eclipse folder and try again? > Build a new feature that omits features available from RPM install > ------------------------------------------------------------------ > > Key: JBDS-3981 > URL: https://issues.jboss.org/browse/JBDS-3981 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.1.0.GA > > Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png > > > What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23016: --------------------------------------- Regarding Windows, as far as I understand it, Windows will offer a gui if a process is requesting admin rights. So in my opinion this will just work on Windows - if you're running devstudio as an admin, you will be shown a full-screen prompt and you just have to agree - no password required. If you're running as a regular user, Windows should prompt you for admin credentials. But I will have to verify this tomorrow. > When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23016 > URL: https://issues.jboss.org/browse/JBIDE-23016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.1.Final > > > The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already). > This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights. > When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22867) JBT could not get projects created by openshift cli tool

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22867?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22867. --------------------------------- > JBT could not get projects created by openshift cli tool > -------------------------------------------------------- > > Key: JBIDE-22867 > URL: https://issues.jboss.org/browse/JBIDE-22867 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.x > Environment: JBoss OpenShift 3 Tools 3.3.0.v20160721-2201 > openshift v3.3.0.12 > kubernetes v1.3.0+57fb9ac > etcd 2.3.0+git > Reporter: Peng Li > Assignee: Andre Dietisheim > Fix For: 4.4.1.Final > > > User could not get projects created by oc command -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23001) Application Wizard: NPE when opening OS 2 wizard from central or shell menu

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23001?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23001. --------------------------------- Verified in DevStudio 10.1.0.GA build ID GA-v20160901-0833-B5918. > Application Wizard: NPE when opening OS 2 wizard from central or shell menu > --------------------------------------------------------------------------- > > Key: JBIDE-23001 > URL: https://issues.jboss.org/browse/JBIDE-23001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: application_wizard, openshift_v2, regression > Fix For: 4.4.1.Final > > > When I am opening a New OpenShift Application wizard for OpenShift 2 connections, I get an NPE. This is caused only when opening wizard from shell menu File - New - OpenShift Application or from Central. > stack trace of NPE: > {code} > Problems occurred when invoking code from plug-in: "org.eclipse.jface". > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.onPageWillGetDeactivated(ConnectionWizardPage.java:408) > at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$3.handlePageChanging(AbstractOpenShiftWizardPage.java:121) > at org.eclipse.jface.wizard.WizardDialog$7.run(WizardDialog.java:1540) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1537) > at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:890) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1177) > at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:876) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:419) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > 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:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4146) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 September 2016