March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21837) OpenShift server adpter editor: link 'Open launch configuration' throws exception

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21837?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-21837: ------------------------------------------ Description: There is no launch configuration tab groups bound to the openshift launch type. As the result, an exception is caught at opening 'Edit Configuration' wizard. The exception is not logged, but user has to click OK on two successive Error and Problem occurred message dialogs and finally gets the wizard with empty Name input and error message 'A name is required for the configuration'. This user unfriendly behaviour may be considered an upstream issue, but the workaround is just to bind an empty list of tab groups. was: There is no launch configuration tab groups bound to the openshift launch type. It may be considered an upstream issue that editor throws NPE on that, but the workaround is just to bind an empty list of tab groups. > OpenShift server adpter editor: link 'Open launch configuration' throws exception > --------------------------------------------------------------------------------- > > Key: JBIDE-21837 > URL: https://issues.jboss.org/browse/JBIDE-21837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Viacheslav Kabanovich > Attachments: ErrorAtEditLaunchConfig.png > > > There is no launch configuration tab groups bound to the openshift launch type. > As the result, an exception is caught at opening 'Edit Configuration' wizard. The exception is not logged, but user has to click OK on two successive Error and Problem occurred message dialogs and finally gets the wizard with empty Name input and error message 'A name is required for the configuration'. > This user unfriendly behaviour may be considered an upstream issue, but the workaround is just to bind an empty list of tab groups. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21837) OpenShift server adpter editor: link 'Open launch configuration' throws exception

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21837?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-21837: ------------------------------------------ Attachment: ErrorAtEditLaunchConfig.png > OpenShift server adpter editor: link 'Open launch configuration' throws exception > --------------------------------------------------------------------------------- > > Key: JBIDE-21837 > URL: https://issues.jboss.org/browse/JBIDE-21837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Viacheslav Kabanovich > Attachments: ErrorAtEditLaunchConfig.png > > > There is no launch configuration tab groups bound to the openshift launch type. > It may be considered an upstream issue that editor throws NPE on that, but the workaround is just to bind an empty list of tab groups. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21837) OpenShift server adpter editor: link 'Open launch configuration' throws exception

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-21837: --------------------------------------------- Summary: OpenShift server adpter editor: link 'Open launch configuration' throws exception Key: JBIDE-21837 URL: https://issues.jboss.org/browse/JBIDE-21837 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta2 Reporter: Viacheslav Kabanovich There is no launch configuration tab groups bound to the openshift launch type. It may be considered an upstream issue that editor throws NPE on that, but the workaround is just to bind an empty list of tab groups. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-712) JBDS-IS 9.0.0 Beta1 - Release Notes

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-712?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-712: ------------------------------------ Thanks, [~apodhrad] Fixed the issues in section 2 and updated the issues listed in 3.2. Added a new section for BPMN2 issues as well. Edit: This comment did not go through yesterday and I didn't realize it. Waiting your ack to fix up anything that needs it and in the meantime, publishing docs so that there is a beta release notes available. > JBDS-IS 9.0.0 Beta1 - Release Notes > ----------------------------------- > > Key: TOOLSDOC-712 > URL: https://issues.jboss.org/browse/TOOLSDOC-712 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create release notes for this release based on Andrej's information. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21791) Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-21791: ----------------------------------------- Done, see the screenshots in https://github.com/jbosstools/jbosstools-forge/pull/157#issuecomment-1940... > Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21791 > URL: https://issues.jboss.org/browse/JBIDE-21791 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.Beta2 > Reporter: Claus Ibsen > Assignee: George Gastaldi > Fix For: 4.3.1.CR1 > > Attachments: eclipse-add.png > > > Similar problem as FORGE-2605 but this time its in Eclipse. > See the attached screenshot, where I have edited the file camel-context.xml, and then run my forge command, which would insert a Camel endpoint at the cursor position. But eclipse has detected a file conflict as in that dialog. > I wonder if the fix should be like in IDEA to save the file before the command is run. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3615) virtual box cannot be installed reliably on windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3615?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3615: ------------------------------------- I see you have it in code implemented with node-windows - awesome. > virtual box cannot be installed reliably on windows > --------------------------------------------------- > > Key: JBDS-3615 > URL: https://issues.jboss.org/browse/JBDS-3615 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > look at docker-toolbox what they do that is different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3615) virtual box cannot be installed reliably on windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3615?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3615: ------------------------------------- self extracting archive which is used for bundled installer asks for elevated privileges, so it should work here OOTB. Electron packager for windows might have an option to elevate privileges for generated installer. > virtual box cannot be installed reliably on windows > --------------------------------------------------- > > Key: JBDS-3615 > URL: https://issues.jboss.org/browse/JBDS-3615 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > look at docker-toolbox what they do that is different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3664) Do we still need/want custom build of vagrant ?

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3664?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3664: ------------------------------------- Last time I was trying to use headless msi, it ignored target location and just installed vagrant to default one /hashicorp/vagrant. I'll test ASAP if it is possible to configure target destination for vagrant when installing from msi. > Do we still need/want custom build of vagrant ? > ----------------------------------------------- > > Key: JBDS-3664 > URL: https://issues.jboss.org/browse/JBDS-3664 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > we seem to install use our custom vagrant build. > Is that still relevant ? > With that we need to test much more since our build could be different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3671?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-3671 at 3/8/16 5:07 PM: ------------------------------------------------------------- Yes, this pacman worked for me and sshd -h would print out help text. was (Author: dgolovin): Yes this pacman worked for me and sshd -h would print out help text. > 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 month

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 commented on JBIDE-21386: ------------------------------------ Jobs have been updated. > 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, jbt-tp-p2diff-460-summary.txt, jbt-tp-p2diff-460.txt, jbtcentral-p2diff_460.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 month

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