February 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3595) dark theme not nice

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3595?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3595: ----------------------------- Priority: Minor (was: Major) > dark theme not nice > ------------------- > > Key: JBDS-3595 > URL: https://issues.jboss.org/browse/JBDS-3595 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, upstream > Affects Versions: 9.1.0.Beta2 > Reporter: Aleksandar Kostadinov > Priority: Minor > Fix For: 9.x > > Attachments: jbds_dark.png > > > Selecting "Dark" them in appearance yields somehow ugly result. Would be nice to be fixed. > !jbds_dark.png|thumbnail! > btw have installed GoClipse, not sure if that matters. Have not checked dark theme before install. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20045) Software/Update page looks bad in Dark mode

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20045?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20045: ------------------------------- Priority: Minor (was: Major) > Software/Update page looks bad in Dark mode > ------------------------------------------- > > Key: JBIDE-20045 > URL: https://issues.jboss.org/browse/JBIDE-20045 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta1 > Reporter: Fred Bricon > Assignee: Snjezana Peco > Priority: Minor > Fix For: 4.3.x > > Attachments: central.png > > > - Enable Eclipse Dark Theme in Preferences > Appearance, > - Open Central, click on the Software Update page > - Make sure Early Access is enabled > - Check this : > !http://content.screencast.com/users/fbricon/folders/Jing/media/679d7466-cba0-42b8-aaf0-8d6b2f35691a/00000113.png! > - grey areas around the checkboxes and the titles > - blue links don't look good > - Early-Access items are not highlighted (even after fixing JBIDE-20007) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3595) dark theme not nice

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3595?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3595: ----------------------------- Fix Version/s: 9.x > dark theme not nice > ------------------- > > Key: JBDS-3595 > URL: https://issues.jboss.org/browse/JBDS-3595 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, upstream > Affects Versions: 9.1.0.Beta2 > Reporter: Aleksandar Kostadinov > Fix For: 9.x > > Attachments: jbds_dark.png > > > Selecting "Dark" them in appearance yields somehow ugly result. Would be nice to be fixed. > !jbds_dark.png|thumbnail! > btw have installed GoClipse, not sure if that matters. Have not checked dark theme before install. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3642) Installer is too opaque - need a debug/verbose mode to track progress and debug failures

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3642: ---------------------------------- Summary: Installer is too opaque - need a debug/verbose mode to track progress and debug failures Key: JBDS-3642 URL: https://issues.jboss.org/browse/JBDS-3642 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.1.0.GA Reporter: Len DiMaggio The install.log created by the installer does not contain a detailed listing of all actions performed by the installer. Setting the install browser into a debug mode ( "set PDKI_DEBUG=true" ) generated additional information, but it is still node a detailed dump of all actions. Can we add a debug/verbose/trace mode? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21782) Adding EAP 7. ER6 server rises a warning on New runtime page

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21782?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21782: -------------------------------------- Assignee: Rob Stryker > Adding EAP 7. ER6 server rises a warning on New runtime page > ------------------------------------------------------------ > > Key: JBIDE-21782 > URL: https://issues.jboss.org/browse/JBIDE-21782 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > > Screenshot: http://i.imgur.com/ObzrfQs.png > The warning is: > {noformat} > This server type expects a version of 6.1 but the server directory is of version 7.0.0.GA. This combination may cause critical errors. {noformat} > I guess it's because ER6 reports version "7.0.0.GA". > For example ER2 doesn't raise the warning (because it still reports as 7.0.0.Beta1). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21778) Styled texts are markable and it is possible to put cursor into them

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21778?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21778: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > Styled texts are markable and it is possible to put cursor into them > -------------------------------------------------------------------- > > Key: JBIDE-21778 > URL: https://issues.jboss.org/browse/JBIDE-21778 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Optional > Labels: openshift_v2, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Currently styled texts for "get started" and "retrieve token" parts (maybe there are other places) are almost perfect. What I found a place for an enhancement is making it similar to labels. I mean don't allow user to put cursor into it (after mouse left click) and marking text would not be possible too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3617) Cannot run vagrant after running installer

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3617?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3617: -------------------------------------- The only remaining issue here is that if a just registered user won't have a RHEL subscription which is required for provision. I think we should create a separate issue for that and resolve this one. > Cannot run vagrant after running installer > ------------------------------------------ > > Key: JBDS-3617 > URL: https://issues.jboss.org/browse/JBDS-3617 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Environment: Windows 10 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Priority: Blocker > Labels: havoc > Attachments: Vagrant.png > > > See attached screenshot - the same error is seen when running with the CDK configured as a runtime - or by running vagrant/vagrant.bat form the CLI after running the installer. > Exception occurred executing command line. > {{Cannot run program c:\DeveloperPlatform\vagrant\bin\vagrant) (in directory {{C:\DeveloperPlatform\cdk\plugins): CreateProcess error=193, %1 is not a valid Win32 application}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3641) Installer - initial run fails, log generated, subsequent run is successful

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3641?page=com.atlassian.jira.plugin.... ] Len DiMaggio closed JBDS-3641. ------------------------------ Resolution: Duplicate Issue This is another variation on a prior installation not being completely "cleaned up" before trying a new install. The cleanup tool/method has to delete files/dirs in both the user's dir tree and the C:/DeveloperPlatform dir, as well as clean up the registry and user's path. > Installer - initial run fails, log generated, subsequent run is successful > -------------------------------------------------------------------------- > > Key: JBDS-3641 > URL: https://issues.jboss.org/browse/JBDS-3641 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Environment: Windows 10 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Attachments: install.log > > > This problem is seen intermittently. Sometimes the initial run of the installer fails - but the subsequent run succeeds. See attached install.log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21771) Simplest java project is imported sometimes as JDT, sometimes not.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21771?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21771: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > Simplest java project is imported sometimes as JDT, sometimes not. > ------------------------------------------------------------------ > > Key: JBIDE-21771 > URL: https://issues.jboss.org/browse/JBIDE-21771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: PlainJavaProject > > > Importing simplest java project (in attachment) gets sometimes imported as "Java, JDT" and sometimes only as "Java". I am not able to provide exact steps to reproduce, as it seems to do that randomly. > Looking at http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles/org.eclips..., project should be detected as JDT, in case ".classpath" is found in the project. Couldn't be the issue the order of executing configurators? Like when Java configurator is called first, it creates .classpath and then JDT configurator is called and it sees the .classpath file. When the order is opposite, JDT is not configured, because .classpath is not there yet? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3575) Add Fedora 22 and 23 to the support matrix

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3575?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3575: -------------------------------------- OK. But we can't resolve this issue until the documentation is updated. > Add Fedora 22 and 23 to the support matrix > ------------------------------------------ > > Key: JBDS-3575 > URL: https://issues.jboss.org/browse/JBDS-3575 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 9.1.0.GA > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2016