October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4102) Headless installation doesn't generate InstallConfigRecord.xml

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4102?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4102: -------------------------------- Fix Version/s: 10.2.0.AM3 > Headless installation doesn't generate InstallConfigRecord.xml > -------------------------------------------------------------- > > Key: JBDS-4102 > URL: https://issues.jboss.org/browse/JBDS-4102 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 10.1.0.AM2 > Environment: Fedora 24, openjdk 1.8.0_102 > Reporter: Lukáš Valach > Assignee: Denis Golovin > Fix For: 10.2.0.AM3 > > Attachments: InstallConfigRecord_missing-terminal.png > > > The installer should create InstallConfigRecord.xml in target folder, it works fine when I install devstudio in standard way (using GUI), but when I use headless installation the installer doesn't create InstallConfigRecord.xml in target folder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4102) Headless installation doesn't generate InstallConfigRecord.xml

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4102?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4102: ----------------------------------- Assignee: Denis Golovin > Headless installation doesn't generate InstallConfigRecord.xml > -------------------------------------------------------------- > > Key: JBDS-4102 > URL: https://issues.jboss.org/browse/JBDS-4102 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 10.1.0.AM2 > Environment: Fedora 24, openjdk 1.8.0_102 > Reporter: Lukáš Valach > Assignee: Denis Golovin > Fix For: 10.2.0.AM3 > > Attachments: InstallConfigRecord_missing-terminal.png > > > The installer should create InstallConfigRecord.xml in target folder, it works fine when I install devstudio in standard way (using GUI), but when I use headless installation the installer doesn't create InstallConfigRecord.xml in target folder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4102) Headless installation doesn't generate InstallConfigRecord.xml

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4102?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4102: -------------------------------- Component/s: upstream > Headless installation doesn't generate InstallConfigRecord.xml > -------------------------------------------------------------- > > Key: JBDS-4102 > URL: https://issues.jboss.org/browse/JBDS-4102 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 10.1.0.AM2 > Environment: Fedora 24, openjdk 1.8.0_102 > Reporter: Lukáš Valach > Attachments: InstallConfigRecord_missing-terminal.png > > > The installer should create InstallConfigRecord.xml in target folder, it works fine when I install devstudio in standard way (using GUI), but when I use headless installation the installer doesn't create InstallConfigRecord.xml in target folder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18526) CordovaSim: Debugger doesn't work properly with the last JDK 8u20

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18526?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18526: ------------------------------------- The upstream issue has been closed - https://bugs.openjdk.java.net/browse/JDK-8090205 The fix should be available in JDK 9 > CordovaSim: Debugger doesn't work properly with the last JDK 8u20 > ----------------------------------------------------------------- > > Key: JBIDE-18526 > URL: https://issues.jboss.org/browse/JBIDE-18526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim, upstream > Affects Versions: 4.2.0.CR2 > Environment: Not reproducible with Oracle JDK 7u67 > Affects Oracle JDK 8u20 and above (Not reproducible with JDK 8u5 and 8u11) > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Labels: upstream > Fix For: 4.4.x > > Attachments: debugger error.png > > > CordovaSim freezes with the following stack trace: > {code} > java.lang.IllegalStateException: Nested event loops are allowed only while handling system events > at com.sun.javafx.tk.quantum.QuantumToolkit.enterNestedEventLoop(QuantumToolkit.java:506) > at com.sun.javafx.webkit.EventLoopImpl.cycle(EventLoopImpl.java:59) > at com.sun.webkit.EventLoop.fwkCycle(EventLoop.java:45) > at com.sun.webkit.Timer.twkFireTimerEvent(Native Method) > at com.sun.webkit.Timer.fireTimerEvent(Timer.java:83) > at com.sun.webkit.Timer.notifyTick(Timer.java:64) > at javafx.scene.web.WebEngine$PulseTimer.lambda$static$44(WebEngine.java:1167) > at javafx.scene.web.WebEngine$PulseTimer$$Lambda$67/10449826.pulse(Unknown Source) > at com.sun.javafx.tk.Toolkit.lambda$runPulse$28(Toolkit.java:314) > at com.sun.javafx.tk.Toolkit$$Lambda$134/26908315.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at com.sun.javafx.tk.Toolkit.runPulse(Toolkit.java:313) > at com.sun.javafx.tk.Toolkit.firePulse(Toolkit.java:340) > at com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:451) > at com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:431) > at com.sun.javafx.tk.quantum.QuantumToolkit.lambda$runToolkit$363(QuantumToolkit.java:298) > at com.sun.javafx.tk.quantum.QuantumToolkit$$Lambda$40/33541029.run(Unknown Source) > at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) > at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:114) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:91) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23307) Provide a menu in Forge view to trigger the forge wizard

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23307?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-23307: ----------------------------------------- Hi [~aurelien.pupier], You mean as a button in the Forge Console? Could you provide a screenshot (or a mockup) of what you mean? Thanks! > Provide a menu in Forge view to trigger the forge wizard > -------------------------------------------------------- > > Key: JBIDE-23307 > URL: https://issues.jboss.org/browse/JBIDE-23307 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Labels: usability > > Having to guess the first time and then to remind the Ctrl+4 shortcut is just impossible. > please provide a menu in Forge view to trigger the action to open the wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23029: ------------------------------------------ [~mlabuda] The tooling currently wont watch (openshift) projects and thus the UI wont get automatically updated when a project is created via core means (not via the UI). The UI needs a manual refresh to display the new project. JBIDE-23184 is where this limitation is tracked. I added a workaround to fix this at [PR|https://github.com/jbosstools/jbosstools-integration-tests/pull/1609/f...]. Please review and accept for merge or point to further issues. Ideally we'd have this merged before we freeze this week. > Integration tests: Tests should be able to run individually > ----------------------------------------------------------- > > Key: JBIDE-23029 > URL: https://issues.jboss.org/browse/JBIDE-23029 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.2.Final > > > We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need). > This is even more true since running the whole suite is a lengthy task. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23307) Provide a menu in Forge view to trigger the forge wizard

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-23307: --------------------------------------- Summary: Provide a menu in Forge view to trigger the forge wizard Key: JBIDE-23307 URL: https://issues.jboss.org/browse/JBIDE-23307 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: forge Affects Versions: 4.4.1.Final Reporter: Aurélien Pupier Having to guess the first time and then to remind the Ctrl+4 shortcut is just impossible. please provide a menu in Forge view to trigger the action to open the wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23307) Provide a menu in Forge view to trigger the forge wizard

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23307?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-23307: ------------------------------------ Labels: usability (was: ) > Provide a menu in Forge view to trigger the forge wizard > -------------------------------------------------------- > > Key: JBIDE-23307 > URL: https://issues.jboss.org/browse/JBIDE-23307 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Labels: usability > > Having to guess the first time and then to remind the Ctrl+4 shortcut is just impossible. > please provide a menu in Forge view to trigger the action to open the wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4103) Prefer JDK over JRE as VM set in devstudio.ini

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBDS-4103: ------------------------------------- Summary: Prefer JDK over JRE as VM set in devstudio.ini Key: JBDS-4103 URL: https://issues.jboss.org/browse/JBDS-4103 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Enhancement Components: platform-installer Reporter: Aurélien Pupier When using JBDS, a lot of people will use Maven and having a JDK by default is better. It allows to launch Maven install with java compilation directly, without extra configuration. (as a side note, do we really want to set a vm? when the Vm is updated, the link is broken and we need to update it) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22816: ------------------------------------------ [~jeffmaury] ok, great, thanks > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Fix For: 4.4.2.AM2 > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016