March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3656) The installer should use Vagrantfile provided by CDK

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3656?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3656: ------------------------------------- [~hardy.ferentschik] Is it going to be one file of we have to start two as explained [here|https://access.redhat.com/documentation/en/red-hat-enterprise-linux-... > The installer should use Vagrantfile provided by CDK > ---------------------------------------------------- > > Key: JBDS-3656 > URL: https://issues.jboss.org/browse/JBDS-3656 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Hardy Ferentschik > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > The installer should be using the {{Vagrantfile}} provided by the CDK (provided it reaches feature parity) instead of the {{Vagrantfile}} provided by the [openshift-vagrant|https://github.com/redhat-developer-tooling/openshift-v...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21600) Upgrade Forge Runtime to 3.0.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21600?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-21600. ------------------------------------- Resolution: Done > Upgrade Forge Runtime to 3.0.0.Final > ------------------------------------ > > Key: JBIDE-21600 > URL: https://issues.jboss.org/browse/JBIDE-21600 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.1.Beta2 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.1.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21600) Upgrade Forge Runtime to 3.0.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21600?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-21600: ------------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-forge/pull/158 (was: https://github.com/jbosstools/jbosstools-forge/pull/154, https://github.com/jbosstools/jbosstools-forge/pull/155) > Upgrade Forge Runtime to 3.0.0.Final > ------------------------------------ > > Key: JBIDE-21600 > URL: https://issues.jboss.org/browse/JBIDE-21600 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.1.Beta2 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.1.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3653) User's home folder with spaces cannot be used by vagrant during install

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3653?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3653: ------------------------------------- [~fbricon] could you try add env var in windows settings {code}VAGRANT_DOTFILE_PATH=c:\FREDBR~1\.vagrant.d{code} Run installer and see if vagrant.up would work? > User's home folder with spaces cannot be used by vagrant during install > ----------------------------------------------------------------------- > > Key: JBDS-3653 > URL: https://issues.jboss.org/browse/JBDS-3653 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > Vagrant complains about > {quote}Wed, 02 Mar 2016 18:04:21 GMT-ERROR: cdk - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.0.0.gem" > The directory where plugins are installed (the Vagrant home directory) > has a space in it. On Windows, there is a bug in Ruby when compiling > plugins into directories with spaces. Please move your Vagrant home > directory to a path without spaces and try again > {quote} > When user home directory have spaces in it, because .vagrant.d file path in turn has spaces as well. For instance: > {code}C:\Users\User Name\.vagrant.d{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3653) User's home folder with spaces cannot be used by vagrant during install

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3653?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-3653 at 3/15/16 2:55 PM: -------------------------------------------------------------- [~fbricon] could you try add env var in windows settings {code}VAGRANT_DOTFILE_PATH=c:\FREDBR~1\.vagrant.d{code} Run installer and see if vagrant up would work? was (Author: dgolovin): [~fbricon] could you try add env var in windows settings {code}VAGRANT_DOTFILE_PATH=c:\FREDBR~1\.vagrant.d{code} Run installer and see if vagrant.up would work? > User's home folder with spaces cannot be used by vagrant during install > ----------------------------------------------------------------------- > > Key: JBDS-3653 > URL: https://issues.jboss.org/browse/JBDS-3653 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > Vagrant complains about > {quote}Wed, 02 Mar 2016 18:04:21 GMT-ERROR: cdk - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.0.0.gem" > The directory where plugins are installed (the Vagrant home directory) > has a space in it. On Windows, there is a bug in Ruby when compiling > plugins into directories with spaces. Please move your Vagrant home > directory to a path without spaces and try again > {quote} > When user home directory have spaces in it, because .vagrant.d file path in turn has spaces as well. For instance: > {code}C:\Users\User Name\.vagrant.d{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21600) Upgrade Forge Runtime to 3.0.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21600?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-21600: ------------------------------------ Summary: Upgrade Forge Runtime to 3.0.0.Final (was: Upgrade Forge Runtime to 3.0.0.CR1) > Upgrade Forge Runtime to 3.0.0.Final > ------------------------------------ > > Key: JBIDE-21600 > URL: https://issues.jboss.org/browse/JBIDE-21600 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.1.Beta2 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.1.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3671) sshd needs to be installed and started

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBDS-3671?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik commented on JBDS-3671: ----------------------------------------- {quote} We seem cannot get rid of cygwin. Mingw based ssh doesn't work with latest Vagrant, some ssh/rsync options incompatibility. I discovered that when was testing vagrant detection in installer. {quote} Ok, that seems to be settled then. Cygwin is used either way and hence we can use the sshd setup via {code}ssh-host-config{code} to install the sshd Windows service. OOI, where in the installer codebase do I find the code dealing with cygwin? Did you manage to get a "silent" cygwin install going? > sshd needs to be installed and started > -------------------------------------- > > Key: JBDS-3671 > URL: https://issues.jboss.org/browse/JBDS-3671 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Hardy Ferentschik > Labels: havoc > Fix For: 9.1.0.CR1 > > > As parts of the Docker story we need to be able to mount the users home directory into the VM (as docker-machine does as well). Only this way the user can then use Docker mounts to mount for example project directories into a Docker container. > docker-machine uses the vbguest additions for that, but we still need to determine whether this is possible for us due to potential licensing issues. > An alternative approach is to use [sshfs|https://github.com/dustymabe/vagrant-sshfs/] and use ssh to mount the user's home directory into the VM. sshfs, however, requires a running sshd on the host. On Windows I am aware of two ways of doing that > * Cygwin - http://docs.oracle.com/cd/E24628_01/install.121/e22624/preinstall_req_cyg... > * Win32-OpenSSH - https://github.com/PowerShell/Win32-OpenSSH > I think the Windows ssh port would be the preferred solution, however, when testing it, the connection failed when using sshfs. I was able to simple ssh from the guest (CDK) to the host (Windows), but when using sshfs the connection would just abort. More investigation is required for using vagrant-sshfs with Win32-OpenSSH. It might just be that the Windows port is not fully functional which would leave use with the cygwin approach. > Bottom line, if we want to use the sshfs approach as an alternative for vbguest additions, we need to get sshd installed one way or the other. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3671) sshd needs to be installed and started

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBDS-3671?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik edited comment on JBDS-3671 at 3/15/16 2:45 PM: ------------------------------------------------------------------ {quote} We seem cannot get rid of cygwin. Mingw based ssh doesn't work with latest Vagrant, some ssh/rsync options incompatibility. I discovered that when was testing vagrant detection in installer. {quote} Ok, that seems to be settled then. Cygwin is used either way and hence we can use the sshd setup via _ssh-host-config_ to install the sshd Windows service. OOI, where in the installer codebase do I find the code dealing with cygwin? Did you manage to get a "silent" cygwin install going? was (Author: hardy.ferentschik): {quote} We seem cannot get rid of cygwin. Mingw based ssh doesn't work with latest Vagrant, some ssh/rsync options incompatibility. I discovered that when was testing vagrant detection in installer. {quote} Ok, that seems to be settled then. Cygwin is used either way and hence we can use the sshd setup via {code}ssh-host-config{code} to install the sshd Windows service. OOI, where in the installer codebase do I find the code dealing with cygwin? Did you manage to get a "silent" cygwin install going? > sshd needs to be installed and started > -------------------------------------- > > Key: JBDS-3671 > URL: https://issues.jboss.org/browse/JBDS-3671 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Hardy Ferentschik > Labels: havoc > Fix For: 9.1.0.CR1 > > > As parts of the Docker story we need to be able to mount the users home directory into the VM (as docker-machine does as well). Only this way the user can then use Docker mounts to mount for example project directories into a Docker container. > docker-machine uses the vbguest additions for that, but we still need to determine whether this is possible for us due to potential licensing issues. > An alternative approach is to use [sshfs|https://github.com/dustymabe/vagrant-sshfs/] and use ssh to mount the user's home directory into the VM. sshfs, however, requires a running sshd on the host. On Windows I am aware of two ways of doing that > * Cygwin - http://docs.oracle.com/cd/E24628_01/install.121/e22624/preinstall_req_cyg... > * Win32-OpenSSH - https://github.com/PowerShell/Win32-OpenSSH > I think the Windows ssh port would be the preferred solution, however, when testing it, the connection failed when using sshfs. I was able to simple ssh from the guest (CDK) to the host (Windows), but when using sshfs the connection would just abort. More investigation is required for using vagrant-sshfs with Win32-OpenSSH. It might just be that the Windows port is not fully functional which would leave use with the cygwin approach. > Bottom line, if we want to use the sshfs approach as an alternative for vbguest additions, we need to get sshd installed one way or the other. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3650) username used for cdk could not be used with vagrant up on cdk

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3650?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3650: ------------------------------------- It should be fixed, but not tested yet with installer. I'll do this when new registration workflow is released. I expect new registered user would need to go only through one T&C's signing page and everything works after installation without additional steps. > username used for cdk could not be used with vagrant up on cdk > -------------------------------------------------------------- > > Key: JBDS-3650 > URL: https://issues.jboss.org/browse/JBDS-3650 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer, upstream > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > in demo by [~dgolovin] he mentions the username used for running the installer could not be used with vagrant registration. > Why is that ? just unique for denis usernames or general problem ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21386) Create and use Neon M5 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21386?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21386: ------------------------------- Attachment: JBIDE-21386_NeonM5_p2diff.txt JBIDE-21386_NeonM5_p2diff_summary.txt JBIDE-21386_NeonM5_JBDS_p2diff.txt JBIDE-21386_NeonM5_JBDS_p2diff_summary.txt JBT p2diff: [^JBIDE-21386_NeonM5_p2diff.txt] [^JBIDE-21386_NeonM5_p2diff_summary.txt] JBDS p2diff: [^JBIDE-21386_NeonM5_JBDS_p2diff.txt] [^JBIDE-21386_NeonM5_JBDS_p2diff_summary.txt] > Create and use Neon M5 target platform > -------------------------------------- > > Key: JBIDE-21386 > URL: https://issues.jboss.org/browse/JBIDE-21386 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: jbds-tp-p2diff-460-summary.txt, jbds-tp-p2diff-460.txt, JBIDE-21386_NeonM5_JBDS_p2diff.txt, JBIDE-21386_NeonM5_JBDS_p2diff_summary.txt, JBIDE-21386_NeonM5_p2diff.txt, JBIDE-21386_NeonM5_p2diff_summary.txt, jbt-tp-p2diff-460-summary.txt, jbt-tp-p2diff-460.txt, jbtcentral-p2diff_460.txt, p2diff.JBIDE-21386.summary.txt, p2diff.JBIDE-21386.txt > > > Prepare TP to use Neon M5 bits. Cloned from JBIDE-20976 so I can start a fresh issue. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build; > * update install/matrix jobs to use new Eclipse JEE/platform binary; > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 March 2016