April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3470) Toolbars + Icons unusable on UHD screens

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3470?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3470: ----------------------------- Fix Version/s: 12.x (was: 10.x) > Toolbars + Icons unusable on UHD screens > ---------------------------------------- > > Key: JBDS-3470 > URL: https://issues.jboss.org/browse/JBDS-3470 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: ui/branding, upstream > Affects Versions: 9.0.0.Beta1 > Environment: Windows + UHD screens > Reporter: Mustafa Musaji > Labels: neon > Fix For: 12.x > > Attachments: hi-res-example.png, jbds-after-scaling.png, wordpad-scaling.png > > > When using JBDS on UHD screen the toolbar is unusable due to it not being resized and too small to use properly. > Upstream: https://bugs.eclipse.org/bugs/show_bug.cgi?id=382972 > I'm raising this for QE to ensure we test this in the next release as it was fixed upstream. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3775) Missing maven.repository.redhat.com

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3775?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3775: ----------------------------- Fix Version/s: 12.x (was: 10.x) > Missing maven.repository.redhat.com > ----------------------------------- > > Key: JBDS-3775 > URL: https://issues.jboss.org/browse/JBDS-3775 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Burr Sutter > Priority: Critical > Labels: havoc > Fix For: 12.x > > > After using the Installer, I select Red Hat Central, OpenShift Application, eap64-basic-sti which then imports the kitchensink project into my workspace, it immediately has compile errors > http://screencast.com/t/y1NFnvaMcJD -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3676) BrowserSim cannot start on openjdk (windows)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3676?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3676: ----------------------------- Fix Version/s: 12.x (was: 10.x) > BrowserSim cannot start on openjdk (windows) > -------------------------------------------- > > Key: JBDS-3676 > URL: https://issues.jboss.org/browse/JBDS-3676 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: browsersim > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Ilya Buziuk > Labels: havoc, openjdk > Fix For: 12.x > > > Running JBDS on Azul OpenJDK 8, Windows 10. > Starting BrowserSim fails with the following error: > {noformat} > BrowserSim has failed to start with the following error: > "To use BrowserSim please install Safari or run BrowserSim with Oracle Java 7u7 and higher." > Also see BrowserSim FAQ. > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3675) NullPointerException during install (no explanation)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3675?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3675: ----------------------------- Fix Version/s: 12.x (was: 10.x) > NullPointerException during install (no explanation) > ---------------------------------------------------- > > Key: JBDS-3675 > URL: https://issues.jboss.org/browse/JBDS-3675 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Environment: Windows 10 Pro 64bit, Oracle JDK 8_74, installer with EAP > Reporter: Hendy Irawan > Assignee: Denis Golovin > Priority: Critical > Fix For: 12.x > > Attachments: jboss1.PNG, jboss2.PNG, jbossdev-install-error.PNG > > > Unfortunately no stacktrace whatsoever :( -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3667) Default post-install window size is very small on Windows 10

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3667?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3667: ----------------------------- Fix Version/s: 12.x (was: 10.x) > Default post-install window size is very small on Windows 10 > ------------------------------------------------------------ > > Key: JBDS-3667 > URL: https://issues.jboss.org/browse/JBDS-3667 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Fix For: 12.x > > Attachments: Small_Window.png > > > See the attached screenshot. This was seen on a 4K Windows 10 laptop. Can we change the default post-install window size? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3593) Enable continuous delivery

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3593?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3593: ----------------------------- Fix Version/s: 12.x (was: 10.x) > Enable continuous delivery > -------------------------- > > Key: JBDS-3593 > URL: https://issues.jboss.org/browse/JBDS-3593 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: build > Affects Versions: 10.0.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 12.x > > > A continuous delivery build is about setting up the necessary checks to make sure that a "snapshot" is in a good enough state to be released (from a releng perspective). > If we have this, then it means that planning can be changed to whatever strategy; without requiring any specific effort to adapt. > I bootstrapped a CI job to start "hosting" all those quality checks: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3591) Publish JBDS on Windows Store

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3591?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3591: ----------------------------- Fix Version/s: 12.x (was: 10.x) > Publish JBDS on Windows Store > ----------------------------- > > Key: JBDS-3591 > URL: https://issues.jboss.org/browse/JBDS-3591 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Mickael Istria > Priority: Optional > Fix For: 12.x > > > We should investigate the possibility of publishing JBDS on Windows Store to make installation from Windows more accessible. > That might also be worth it for the CDK installer. > cc [~akazakov] [~maxandersen] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3580) Limit installation path input field to some reasonable length

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3580?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3580: ----------------------------- Fix Version/s: 12.x (was: 10.x) > Limit installation path input field to some reasonable length > ------------------------------------------------------------- > > Key: JBDS-3580 > URL: https://issues.jboss.org/browse/JBDS-3580 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.Beta2 > Environment: Fedora 22 x86-64 > jboss-devstudio-9.1.0.Beta2-v20160111-2015-B224-installer-standalone.jar > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 12.x > > > When selecting the installation path, you can type in pretty much anything. So I tried a folder with a name of about 30k characters. Clicking next crashed Gnome. > It might be a good idea to implement some reasonable limits. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3577) 'JBDSIS EA Components' entry remains in available features after installing it from EA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3577?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3577: ----------------------------- Fix Version/s: 12.x (was: 10.x) > 'JBDSIS EA Components' entry remains in available features after installing it from EA > -------------------------------------------------------------------------------------- > > Key: JBDS-3577 > URL: https://issues.jboss.org/browse/JBDS-3577 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 9.1.0.Beta1 > Reporter: Jan Richter > Priority: Minor > Fix For: 12.x > > > Install JBDSIS components from central early access -> the JBDSIS Early Access Components still shows up in central as 'Not yet available' in the available features in software/update. > The only way to make it go away is to enable EA and show installed at the same time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3896?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3896: ----------------------------- Fix Version/s: 12.x (was: 10.x) > 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 JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 12.x > > 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 (v7.5.0#75005)

7 years, 11 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 April 2018