February 2019 - jbosstools-issues

[JBoss JIRA] (JBDS-4756) Cannot start devstudio on mac os with jdk 11

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4756?page=com.atlassian.jira.plugin.... ] Ondrej Dockal commented on JBDS-4756: ------------------------------------- I tried myself on the CCI mac (bigmek). Installation with jdk 11 went alright, but when trying to run the devstudio I gotthe same message. My guess is that this is caused by slow network access to jdk which resides on shared drive. (/qa/tools). I will my validate my assumptions... > Cannot start devstudio on mac os with jdk 11 > -------------------------------------------- > > Key: JBDS-4756 > URL: https://issues.jboss.org/browse/JBDS-4756 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.11.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Critical > Fix For: 12.x > > Attachments: Screenshot_20190204_115602.png > > > I can easily install devstudio on mac os with default jdk 11 (from /qa/tools/opt/osx/jdk11_last) but I cannot make it start. No other errors or warnings except the one here: > !Screenshot_20190204_115602.png|thumbnail! > More info links [here|https://support.apple.com/kb/DL1572?locale=en_US]. > I can also see installer [tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] failures on mac os 10.12 and 10.13 with this tack trace: > {code} > java.awt.HeadlessException > at java.desktop/sun.awt.HeadlessToolkit.getScreenSize(HeadlessToolkit.java:186) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:244) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:237) > at com.jboss.jbds.installer.test.InstallerTest.testInstall(InstallerTest.java:49) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at com.sun.proxy.$Proxy0.invoke(Unknown Source) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) > {code} > It might be possible to at least to try the installation and run on some bare metal to verify this error. Could someone possibly assist here, please? I have a suspicion that it might be performance related as the time needed to even open the jdk folder on the shared drive takes quite some time. Thanks! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4756) Cannot start devstudio on mac os with jdk 11

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4756?page=com.atlassian.jira.plugin.... ] Ondrej Dockal reassigned JBDS-4756: ----------------------------------- Assignee: Ondrej Dockal (was: Jeff MAURY) > Cannot start devstudio on mac os with jdk 11 > -------------------------------------------- > > Key: JBDS-4756 > URL: https://issues.jboss.org/browse/JBDS-4756 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.11.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 12.x > > Attachments: Screenshot_20190204_115602.png > > > I can easily install devstudio on mac os with default jdk 11 (from /qa/tools/opt/osx/jdk11_last) but I cannot make it start. No other errors or warnings except the one here: > !Screenshot_20190204_115602.png|thumbnail! > More info links [here|https://support.apple.com/kb/DL1572?locale=en_US]. > I can also see installer [tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] failures on mac os 10.12 and 10.13 with this tack trace: > {code} > java.awt.HeadlessException > at java.desktop/sun.awt.HeadlessToolkit.getScreenSize(HeadlessToolkit.java:186) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:244) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:237) > at com.jboss.jbds.installer.test.InstallerTest.testInstall(InstallerTest.java:49) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at com.sun.proxy.$Proxy0.invoke(Unknown Source) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) > {code} > It might be possible to at least to try the installation and run on some bare metal to verify this error. Could someone possibly assist here, please? I have a suspicion that it might be performance related as the time needed to even open the jdk folder on the shared drive takes quite some time. Thanks! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25050: ---------------------------------- Sprint: devex #151 June 2018, devex #163 March 2019 (was: devex #151 June 2018) > Prepare windows image with hyperv > --------------------------------- > > Key: JBIDE-25050 > URL: https://issues.jboss.org/browse/JBIDE-25050 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.5.1.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: jenkins > Fix For: 4.11.x > > Attachments: error.log > > > Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label. > * Provision win10-x64-jbds (as some changes were made to jbds script) > * Install manually HyperV in fresh windows image > * Add new virtual switch > * Set env. variable HYPERV_VIRTUAL_SWITCH > * Add user into Hyper-V Administrators group > * Test whether cdk can be run on the slave -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26322) Integration Tests: Enhanced Spring Boot support for server adapter

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26322?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26322: ---------------------------------- Sprint: devex #162 February 2019 (was: devex #162 February 2019, devex #163 March 2019) > Integration Tests: Enhanced Spring Boot support for server adapter > ------------------------------------------------------------------ > > Key: JBIDE-26322 > URL: https://issues.jboss.org/browse/JBIDE-26322 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.9.0.AM2 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Labels: integration_tests > Fix For: 4.11.0.AM1 > > > https://tools.jboss.org/documentation/whatsnew/jbosstools/4.6.0.Final.htm... > https://tools.jboss.org/documentation/whatsnew/jbosstools/4.5.2.Final.htm... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26322) Integration Tests: Enhanced Spring Boot support for server adapter

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26322?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26322. --------------------------------- Resolution: Done PR is merged, closing. > Integration Tests: Enhanced Spring Boot support for server adapter > ------------------------------------------------------------------ > > Key: JBIDE-26322 > URL: https://issues.jboss.org/browse/JBIDE-26322 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.9.0.AM2 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Labels: integration_tests > Fix For: 4.11.0.AM1 > > > https://tools.jboss.org/documentation/whatsnew/jbosstools/4.6.0.Final.htm... > https://tools.jboss.org/documentation/whatsnew/jbosstools/4.5.2.Final.htm... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26278) Fix failing hibernate itests

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26278?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-26278: ------------------------------------- Assignee: Josef Kopriva (was: Pavol Srna) > Fix failing hibernate itests > ----------------------------- > > Key: JBIDE-26278 > URL: https://issues.jboss.org/browse/JBIDE-26278 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Pavol Srna > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.11.0.Final > > Attachments: log.txt > > > TBD -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26278) Fix failing hibernate itests

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26278?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26278: ---------------------------------- Fix Version/s: 4.11.0.Final (was: 4.11.x) > Fix failing hibernate itests > ----------------------------- > > Key: JBIDE-26278 > URL: https://issues.jboss.org/browse/JBIDE-26278 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Pavol Srna > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.11.0.Final > > Attachments: log.txt > > > TBD -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26278) Fix failing hibernate itests

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26278?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26278: ---------------------------------- Sprint: devex #154 September 2018, devex #155 September 2018, devex #163 March 2019 (was: devex #154 September 2018, devex #155 September 2018) > Fix failing hibernate itests > ----------------------------- > > Key: JBIDE-26278 > URL: https://issues.jboss.org/browse/JBIDE-26278 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Pavol Srna > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.11.0.Final > > Attachments: log.txt > > > TBD -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26549) Projects from Red Hat Central are containing errors in it (removed package in java 11)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26549?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26549: ------------------------------- Sprint: devex #162 February 2019, devex #163 March 2019 (was: devex #162 February 2019) > Projects from Red Hat Central are containing errors in it (removed package in java 11) > -------------------------------------------------------------------------------------- > > Key: JBIDE-26549 > URL: https://issues.jboss.org/browse/JBIDE-26549 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.11.0.AM1 > Environment: OS X 10.13.6 > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.11.0.AM1 > > > 2 projects from RH central shows errors after import (removed package in java 11): > - JAVA EE "jboss-javaee-webapp" project > - HTML 5 "jboss-as-kitchensink-html5-mobile" project > There is invalid dependency "javax.xml.bind.annotation.XmlRootElement". Description and solution described on Stack Overflow https://stackoverflow.com/questions/52502189/java-11-package-javax-xml-bi.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26454) Proxy usage within QE teams, needs and requirements for deploying

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26454?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26454: ------------------------------- Sprint: devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019 (was: devex #159 December 2018, devex #161 January 2019, devex #162 February 2019) > Proxy usage within QE teams, needs and requirements for deploying > ----------------------------------------------------------------- > > Key: JBIDE-26454 > URL: https://issues.jboss.org/browse/JBIDE-26454 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.10.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: quality > Fix For: 4.11.0.AM1 > > > Find out: > * existing solutions within RH > * needs of other teams > * usability of open source proxy technologies/solutions > * usage among different OS -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 February 2019