May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3902) devstudio won't install using latest installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3902?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3902: ----------------------------- > devstudio won't install using latest installer > ---------------------------------------------- > > Key: JBDS-3902 > URL: https://issues.jboss.org/browse/JBDS-3902 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Environment: devstudio-platform-10.0.0-Alpha1-20160517-157-installer > Reporter: Radim Hopp > Assignee: Jan Richter > Fix For: 10.0.0.Alpha2 > > > {noformat} > Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Execute c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds.jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds-autoinstall.xml SUCCESS > Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Append CDKServer runtime information to JBDS runtime location > Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds - Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties' > Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds failed to install: Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties'{noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3902) devstudio won't install using latest installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3902?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3902: -------------------------------- > devstudio won't install using latest installer > ---------------------------------------------- > > Key: JBDS-3902 > URL: https://issues.jboss.org/browse/JBDS-3902 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Environment: devstudio-platform-10.0.0-Alpha1-20160517-157-installer > Reporter: Radim Hopp > Assignee: Jan Richter > Fix For: 10.0.0.Alpha2 > > > {noformat} > Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Execute c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds.jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds-autoinstall.xml SUCCESS > Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Append CDKServer runtime information to JBDS runtime location > Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds - Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties' > Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds failed to install: Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties'{noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3902) devstudio won't install using latest installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3902?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3902: -------------------------------- Description: {noformat} Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Execute c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds.jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds-autoinstall.xml SUCCESS Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Append CDKServer runtime information to JBDS runtime location Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds - Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties' Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds failed to install: Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties'{noformat} was: {noformat} Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Execute c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds.jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds-autoinstall.xml SUCCESS Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Append CDKServer runtime information to JBDS runtime location Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds - Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties' Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds failed to install: Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties'{noformat} > devstudio won't install using latest installer > ---------------------------------------------- > > Key: JBDS-3902 > URL: https://issues.jboss.org/browse/JBDS-3902 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Environment: devstudio-platform-10.0.0-Alpha1-20160517-157-installer > Reporter: Radim Hopp > Assignee: Jan Richter > Fix For: 10.0.0.Alpha2 > > > {noformat} > Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Execute c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds.jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds-autoinstall.xml SUCCESS > Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Append CDKServer runtime information to JBDS runtime location > Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds - Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties' > Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds failed to install: Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties'{noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3902) devstudio won't install using latest installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3902?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3902: -------------------------------- Description: {noformat} Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Execute c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds.jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds-autoinstall.xml SUCCESS Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Append CDKServer runtime information to JBDS runtime location Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds - Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties' Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds failed to install: Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties'{noformat} was: {noformat} Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Execute c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds.jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds-autoinstall.xml SUCCESS Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Append CDKServer runtime information to JBDS runtime location Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds - Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties' Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds failed to install: Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties'{noformat} > devstudio won't install using latest installer > ---------------------------------------------- > > Key: JBDS-3902 > URL: https://issues.jboss.org/browse/JBDS-3902 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Environment: devstudio-platform-10.0.0-Alpha1-20160517-157-installer > Reporter: Radim Hopp > Assignee: Jan Richter > Fix For: 10.0.0.Alpha2 > > > {noformat} > Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Execute c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds.jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds-autoinstall.xml SUCCESS > Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Append CDKServer runtime information to JBDS runtime location > Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds - Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties' > Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds failed to install: Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties'{noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3902) devstudio won't install using latest installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3902?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3902: -------------------------------- Status: New (was: New) > devstudio won't install using latest installer > ---------------------------------------------- > > Key: JBDS-3902 > URL: https://issues.jboss.org/browse/JBDS-3902 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Environment: devstudio-platform-10.0.0-Alpha1-20160517-157-installer > Reporter: Radim Hopp > Assignee: Jan Richter > Fix For: 10.0.0.Alpha2 > > > {noformat} > Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Execute c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds.jar,C:\Users\jboss-qa\AppData\Local\Temp\jbds-autoinstall.xml SUCCESS > Mon, 23 May 2016 09:24:44 GMT-INFO: jbds - Append CDKServer runtime information to JBDS runtime location > Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds - Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties' > Mon, 23 May 2016 09:24:44 GMT-ERROR: jbds failed to install: Error: ENOENT: no such file or directory, open 'c:\DeveloperPlatform\developer-studio\studio\runtime_locations.properties'{noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3903: ------------------------------------- Suite Installer (former Platform Installer) does not detect or install docker. Main scenario is using VirtualBox VM for vagrant. After installation you start CDK in server view and when VM is up it creates connection in docker view automatically. I agree that this is also good scenario especially after installer will let skip CDK installation and install DevStudio only, would be good to be able to use Docker Tooling OOTB. Not sure if docker configuration should be on Installer or Tooling side though. First idea is to have at least something in Docker Connection View or in New Connection wizard saying: "Make sure you started Docker service" in case of system cannot detect local running docker. [~akazakov], [~fbricon] WDYT? > Platform Installer does not Setup Docker Env-Vars > ------------------------------------------------- > > Key: JBDS-3903 > URL: https://issues.jboss.org/browse/JBDS-3903 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: docker, platform-installer > Affects Versions: 10.0.0.Alpha1 > Environment: Windows > Reporter: Thomas Mäder > Assignee: Denis Golovin > > I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection. > Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection. > As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21477) Server adapter wizard: listed services wont change if I go back and select a different connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21477?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21477: ------------------------------------------ [~akazakov] sorry, forgot somehow. Reverted in master, reopening. created new PR https://github.com/jbosstools/jbosstools-openshift/pull/1178 > Server adapter wizard: listed services wont change if I go back and select a different connection > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-21477 > URL: https://issues.jboss.org/browse/JBIDE-21477 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.0.Alpha3 > > Attachments: services.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21477) Server adapter wizard: listed services wont change if I go back and select a different connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21477?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21477: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/886, https://github.com/jbosstools/jbosstools-openshift/pull/1174, https://github.com/jbosstools/jbosstools-openshift/pull/1178 (was: https://github.com/jbosstools/jbosstools-openshift/pull/886, https://github.com/jbosstools/jbosstools-openshift/pull/1174) > Server adapter wizard: listed services wont change if I go back and select a different connection > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-21477 > URL: https://issues.jboss.org/browse/JBIDE-21477 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.0.Alpha3 > > Attachments: services.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3896) Unable to install breakpoint even if line number set to be generated

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-3896?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-3896: ------------------------------------- I am not sure I understand the issue. The patch requires the org.eclipse.ui.startup ext. point and needs to be run only when starting JBDS/JBT the first time. I have added it to the o.j.t.runtime.ui plugin because we already have such an ext. point in this plugin. If we want to add it to another plugin, we will have to create a new o.e.ui.startup ext. point. > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBDS-3896 > URL: https://issues.jboss.org/browse/JBDS-3896 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: upstream > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 10.0.0.Alpha3 > > Attachments: breakpoint-error.png, compiler-settings.png, html5-page.png, lineNumber.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3903: -------------------------------- Component/s: docker > Platform Installer does not Setup Docker Env-Vars > ------------------------------------------------- > > Key: JBDS-3903 > URL: https://issues.jboss.org/browse/JBDS-3903 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: docker, platform-installer > Affects Versions: 10.0.0.Alpha1 > Environment: Windows > Reporter: Thomas Mäder > Assignee: Denis Golovin > > I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection. > Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection. > As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows. -- 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 May 2016