June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3939) Update devsuite version number to 1.0.0-GA

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3939?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3939. ----------------------------- Verified with B182. > Update devsuite version number to 1.0.0-GA > ------------------------------------------ > > Key: JBDS-3939 > URL: https://issues.jboss.org/browse/JBDS-3939 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3803) Add JavaVM version detection and validation

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3803?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3803: ----------------------------------- [~dgolovin], are we going to support Java 9 as well? It would need a new regex to check the version because of the new pattern it uses, > Add JavaVM version detection and validation > ------------------------------------------- > > Key: JBDS-3803 > URL: https://issues.jboss.org/browse/JBDS-3803 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3718) Detected/selected JDK always reported as invalid

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3718?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3718. ----------------------------- Closing, as the progress is now tracked in JBDS-3803. > Detected/selected JDK always reported as invalid > ------------------------------------------------ > > Key: JBDS-3718 > URL: https://issues.jboss.org/browse/JBDS-3718 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.GA > > > The installer correctly detects a JDK but still reports it as invalid. Same goes for selecting an installation of JDK - all checks pass but still the message says the installation is invalid. > It does not seem to be a problem with the detection logic - it returns correct values for me. My guess would be that something is incorrectly propagated to the UI, but I haven't been able to find the source yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3753) Installer forces using detected JDK, tries to install JBDS with the bundled Java anyway

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3753?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3753. ----------------------------- Closing as outdated. > Installer forces using detected JDK, tries to install JBDS with the bundled Java anyway > --------------------------------------------------------------------------------------- > > Key: JBDS-3753 > URL: https://issues.jboss.org/browse/JBDS-3753 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Environment: Setup-bundled-0.0.2-20160401-28 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.GA > > > Using bundled installer build 28 - confirmation page will not let me use the bundled JDK if it detects a pre-existing JDK somewhere else. > Once the installation is triggered, JDK goes straight to finished (not a problem under these circumstances) but JBDS fails right away and the log says: > {noformat} > Fri, 01 Apr 2016 07:20:44 GMT-INFO: jbds - Execute c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jbossqa\AppData\Local\Temp\7zSE006.tmp\jbds.jar,C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 01 Apr 2016 07:20:44 GMT-ERROR: jbds - Error: spawn c:\DeveloperPlatform\jdk8\bin\java.exe ENOENT > Fri, 01 Apr 2016 07:20:44 GMT-ERROR: jbds - > Fri, 01 Apr 2016 07:20:44 GMT-ERROR: jbds failed to install: Error: spawn c:\DeveloperPlatform\jdk8\bin\java.exe ENOENT > {noformat} > So basically, I can't get it to install the bundled JDK but it will still try to use it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3686) Installer is unpredictable - failing in diff actions

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3686?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3686. ----------------------------- None of these issues have been seen for quite a while now, so I'll close this. If some bug of this nature appears, I suggest opening a new jira. > Installer is unpredictable - failing in diff actions > ---------------------------------------------------- > > Key: JBDS-3686 > URL: https://issues.jboss.org/browse/JBDS-3686 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Environment: Windows 10, installer built from src > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Critical > Labels: havoc > Fix For: 10.0.0.GA > > Attachments: Attempt_1.png, Attempt_2.png, Attempt_3.png, install_log_1.txt, install_log_2.txt, install_log_3.txt > > > See attached log files and screenshots - installer faled in different locations on 3 attempts. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3909) rebrand dev platform installer as Red Hat Development Suite

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3909?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3909. ----------------------------- > rebrand dev platform installer as Red Hat Development Suite > ----------------------------------------------------------- > > Key: JBDS-3909 > URL: https://issues.jboss.org/browse/JBDS-3909 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.0.0.GA > > Attachments: RH_DevelopmentSuite_Logo.svg, updated-branding.png > > > Per decision made last week in https://trello.com/c/Cbo0q8TT/99-rebrand-jbds-as-rhds-using-rhd-logo and https://docs.google.com/presentation/d/1Ub-egAS7nbzFijKCTnUk7GJP8WPCQC28q... we need to refactor the platform installer to be the Development Suite installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22501) CDK stuck on Starting... after launch

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22501?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22501. --------------------------------- Closing for the time being. > CDK stuck on Starting... after launch > ------------------------------------- > > Key: JBIDE-22501 > URL: https://issues.jboss.org/browse/JBIDE-22501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.0.Final > > > This happened to me a few times and I think I mentioned it in a JIRA, but AFAIK there is no separate JIRA for this. > This is what I did today (verifying JBDS-3739): > 1. Start my Eclipse Neon RC2 > 2. Updated Eclipse > 3. Updated Docker Tools to latest nightly > 4. Installed nightly JBoss Tools Abridged > 5. Set up cdk server (CDK 2.0 on my disk, already set up and started several times before) > 6. Start CDK server > Everything fine here - after some time it's Started, I accepted the OpenShift cert, Docker connection worked. > 7. Stop CDK server > 8. Start CDK server > This time it's stuck on Starting... even though I can see from the console that the vagrant box started: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Clearing any previously set forwarded ports... > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Remote connection disconnect. Retrying... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Configuring and enabling network interfaces... > ==> default: Registering box with vagrant-registration... > ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Rsyncing folder: /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/ => /vagrant > ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision` > ==> default: flag to force provisioning. Provisioners marked to run always will still run. > {code} > Now it will probably time out and stop the server. And most probably next start will work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3942) Document (and verify) the current operation of the platform installer

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3942?page=com.atlassian.jira.plugin.... ] Jan Richter edited comment on JBDS-3942 at 6/10/16 2:48 AM: ------------------------------------------------------------ Ad component selection and dependencies: the user is also required to have/install virtualbox, vagrant and cygwin (cygwin is not detected by the installer though) if they choose to install CDK. was (Author: jrichter1): Ad component selection and dependencies: the user is also required to have/install virtualbox, vagrant and cygwin if they choose to install CDK. > Document (and verify) the current operation of the platform installer > ---------------------------------------------------------------------- > > Key: JBDS-3942 > URL: https://issues.jboss.org/browse/JBDS-3942 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Len DiMaggio > Priority: Critical > Fix For: 10.0.0.GA > > > We have to be careful to test and document the operation of the installer for the release: > Component detection as performed that the bundled platform installer has recently changed. It's important that we communicate clearly to our users how this detection is functioning as of today, and what their options are for running the installer. > The installer installs these (6) high-level components: > * CDK > * Cygwin > * VirtialBox > * Vagrant > * JDK > * DevStudio > Topic: Component Detection Performed by The Installer: > As of today, the installer is able to detect these components: > * Java > * VirtualBox > * Vagrant > If a user runs the installer, and one of these detectable components is installed, the installer will verify that the version of the installed component is supported by the Developer Platform. > If the version of the detected component installed is not supported, an error will be reported to the user. The installer will not automatically update the detected installed component to a supported version. > If the version of the installed component is supported by the Developer Platform, the installer will not overwrite that installed component. > Topic: Components Auto-Selected by the Installer > If the installer is run on a system with none of the high level components pre-installed, the installer should have all components auto-selected to be installed. > Topic: Optionally Installing Components > As of today, users can choose to install selected components singly with the installer. The only dependency should be that if the user attempts to install DevStudio alone, the installer will require the user to also install the JDK at the same time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22501) CDK stuck on Starting... after launch

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22501?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22501: --------------------------------------- I agree with closing it. There's just nothing we can do now when it's not really reproducible - I haven't seen it in the last week. > CDK stuck on Starting... after launch > ------------------------------------- > > Key: JBIDE-22501 > URL: https://issues.jboss.org/browse/JBIDE-22501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.0.Final > > > This happened to me a few times and I think I mentioned it in a JIRA, but AFAIK there is no separate JIRA for this. > This is what I did today (verifying JBDS-3739): > 1. Start my Eclipse Neon RC2 > 2. Updated Eclipse > 3. Updated Docker Tools to latest nightly > 4. Installed nightly JBoss Tools Abridged > 5. Set up cdk server (CDK 2.0 on my disk, already set up and started several times before) > 6. Start CDK server > Everything fine here - after some time it's Started, I accepted the OpenShift cert, Docker connection worked. > 7. Stop CDK server > 8. Start CDK server > This time it's stuck on Starting... even though I can see from the console that the vagrant box started: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Clearing any previously set forwarded ports... > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Remote connection disconnect. Retrying... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Configuring and enabling network interfaces... > ==> default: Registering box with vagrant-registration... > ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Rsyncing folder: /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/ => /vagrant > ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision` > ==> default: flag to force provisioning. Provisioners marked to run always will still run. > {code} > Now it will probably time out and stop the server. And most probably next start will work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3942) Document (and verify) the current operation of the platform installer

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3942?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3942: ----------------------------------- Ad component selection and dependencies: the user is also required to have/install virtualbox, vagrant and cygwin if they choose to install CDK. > Document (and verify) the current operation of the platform installer > ---------------------------------------------------------------------- > > Key: JBDS-3942 > URL: https://issues.jboss.org/browse/JBDS-3942 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Len DiMaggio > Priority: Critical > Fix For: 10.0.0.GA > > > We have to be careful to test and document the operation of the installer for the release: > Component detection as performed that the bundled platform installer has recently changed. It's important that we communicate clearly to our users how this detection is functioning as of today, and what their options are for running the installer. > The installer installs these (6) high-level components: > * CDK > * Cygwin > * VirtialBox > * Vagrant > * JDK > * DevStudio > Topic: Component Detection Performed by The Installer: > As of today, the installer is able to detect these components: > * Java > * VirtualBox > * Vagrant > If a user runs the installer, and one of these detectable components is installed, the installer will verify that the version of the installed component is supported by the Developer Platform. > If the version of the detected component installed is not supported, an error will be reported to the user. The installer will not automatically update the detected installed component to a supported version. > If the version of the installed component is supported by the Developer Platform, the installer will not overwrite that installed component. > Topic: Components Auto-Selected by the Installer > If the installer is run on a system with none of the high level components pre-installed, the installer should have all components auto-selected to be installed. > Topic: Optionally Installing Components > As of today, users can choose to install selected components singly with the installer. The only dependency should be that if the user attempts to install DevStudio alone, the installer will require the user to also install the JDK at the same time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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