March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3654) Virtual machine image registration should check if box with the same name already registered

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3654?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3654: ----------------------------------- Assignee: Denis Golovin > Virtual machine image registration should check if box with the same name already registered > -------------------------------------------------------------------------------------------- > > Key: JBDS-3654 > URL: https://issues.jboss.org/browse/JBDS-3654 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.GA > > > Vagrant leave %HOME%/.vagrant.d/boxes/cdk_v2 after DeveloperPlatform installation is done at least once. Then new installation fails do add the vm box with the same name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3682) Online installer reports missing package.js file

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3682?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3682: -------------------------------- Description: Installer now files to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up. Right way to reference package json would be different for development and runtime (see attached PR); was: Installer now files to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up. Right way to reference package json would be: {code}var pjson = require(path.join(__dirname,'../package.json'));{code} > Online installer reports missing package.js file > ------------------------------------------------ > > Key: JBDS-3682 > URL: https://issues.jboss.org/browse/JBDS-3682 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > > Installer now files to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up. > Right way to reference package json would be different for development and runtime (see attached PR); -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3682) Online installer reports missing package.js file

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3682?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3682: -------------------------------- Priority: Blocker (was: Major) > Online installer reports missing package.js file > ------------------------------------------------ > > Key: JBDS-3682 > URL: https://issues.jboss.org/browse/JBDS-3682 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > > Installer now files to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up. > Right way to reference package json would be different for development and runtime (see attached PR); -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3682) Online installer reports missing package.js file

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3682?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3682: -------------------------------- Git Pull Request: https://github.com/redhat-developer-tooling/developer-platform-install/pu... (was: https://github.com/redhat-developer-tooling/developer-platform-install/pu...) > Online installer reports missing package.js file > ------------------------------------------------ > > Key: JBDS-3682 > URL: https://issues.jboss.org/browse/JBDS-3682 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > > Installer now files to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up. > Right way to reference package json would be: > {code}var pjson = require(path.join(__dirname,'../package.json'));{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21895) Resource name collisions after deleting and recreating the application

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21895: --------------------------------------- The other thing of note here is what is meant by 'application'? There is no such hard concept for OpenShift. I thought the eclipse 'new-app' functionality is supposed to perform a name check before creating and provide the user with an opportunity to modify it. The options suggested by [~scabanovich] are additional options that are reasonable. I think we also need to educate users more about openshift that these operations they are doing are not transactional and there should be limited expectations with 'new-app' and 'deploy image'. > Resource name collisions after deleting and recreating the application > ---------------------------------------------------------------------- > > Key: JBIDE-21895 > URL: https://issues.jboss.org/browse/JBIDE-21895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Fix For: 4.4.x > > Attachments: Screen Shot 2016-03-17 at 16.19.05.png > > > 1) Create e.g. node application in a openshift project > 2) Right click from project explorer -> Delete the application > 3) repeat step 1) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3682) Online installer reports missing package.js file

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3682?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3682: ------------------------------------- this approach with __dirname is not going to work everywhere. In mocha test __dirname value is c:/${projectRoot}/browser, in generated electron app it is where DeveloperPlatformInstaller.exe file is , in karma it is undefined. > Online installer reports missing package.js file > ------------------------------------------------ > > Key: JBDS-3682 > URL: https://issues.jboss.org/browse/JBDS-3682 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > > Installer now files to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up. > Right way to reference package json would be: > {code}var pjson = require(path.join(__dirname,'../package.json'));{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21895) Resource name collisions after deleting and recreating the application

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21895: ----------------------------------------------- A simple solution for now that would not need changes in restclient may be to ask user 'Do you want to replace these resources?' - and if yes, then do two jobs, remove resources and create application. > Resource name collisions after deleting and recreating the application > ---------------------------------------------------------------------- > > Key: JBIDE-21895 > URL: https://issues.jboss.org/browse/JBIDE-21895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Fix For: 4.4.x > > Attachments: Screen Shot 2016-03-17 at 16.19.05.png > > > 1) Create e.g. node application in a openshift project > 2) Right click from project explorer -> Delete the application > 3) repeat step 1) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21582) Server adapter: always publishes on Eclipse startup

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21582?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21582: ----------------------------------- Assignee: Rob Stryker (was: Fred Bricon) > Server adapter: always publishes on Eclipse startup > --------------------------------------------------- > > Key: JBIDE-21582 > URL: https://issues.jboss.org/browse/JBIDE-21582 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > Attachments: usage-on-splash.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21895) Resource name collisions after deleting and recreating the application

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21895: ----------------------------------------------- I see some relation of this issue and JBIDE-21462. When application is created, needed resources are created in openshift project. When application is deleted, it does not mean that used by it resources from openshift project must be deleted, they can be shared. But when 'collisions' are found, maybe user may be given an option to change name of resource to be created or state that he will reuse already existing resource? > Resource name collisions after deleting and recreating the application > ---------------------------------------------------------------------- > > Key: JBIDE-21895 > URL: https://issues.jboss.org/browse/JBIDE-21895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Fix For: 4.4.x > > Attachments: Screen Shot 2016-03-17 at 16.19.05.png > > > 1) Create e.g. node application in a openshift project > 2) Right click from project explorer -> Delete the application > 3) repeat step 1) -- 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: ------------------------------------- Any help is welcome :) > 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: 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

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