June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19987) Batch diagram popup is not readable

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19987?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19987: ----------------------------------- Priority: Minor (was: Major) > Batch diagram popup is not readable > ----------------------------------- > > Key: JBIDE-19987 > URL: https://issues.jboss.org/browse/JBIDE-19987 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Daniel Azarov > Priority: Minor > Fix For: 4.3.0.CR1 > > Attachments: batch-editor.png > > > In Batch editor, Diagram tab, when I create a new step, select it and roll mouse over action buttons the text is not readable very well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19987) Batch diagram popup is not readable

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19987?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19987: ---------------------------------------- It may be an upstream (Sapphire) issue. Need to investigate. > Batch diagram popup is not readable > ----------------------------------- > > Key: JBIDE-19987 > URL: https://issues.jboss.org/browse/JBIDE-19987 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Fix For: 4.3.0.CR1 > > Attachments: batch-editor.png > > > In Batch editor, Diagram tab, when I create a new step, select it and roll mouse over action buttons the text is not readable very well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19987) Batch diagram popup is not readable

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19987?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19987: ----------------------------------- Fix Version/s: 4.3.0.CR1 > Batch diagram popup is not readable > ----------------------------------- > > Key: JBIDE-19987 > URL: https://issues.jboss.org/browse/JBIDE-19987 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Fix For: 4.3.0.CR1 > > Attachments: batch-editor.png > > > In Batch editor, Diagram tab, when I create a new step, select it and roll mouse over action buttons the text is not readable very well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3456) Resizing JBDS window right after is appears crashes it with GTK3

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3456?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3456: -------------------------------------- [~snjeza] could you pleae take a look. > Resizing JBDS window right after is appears crashes it with GTK3 > ---------------------------------------------------------------- > > Key: JBDS-3456 > URL: https://issues.jboss.org/browse/JBDS-3456 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: ui/branding > Affects Versions: 9.0.0.Beta1 > Reporter: Jan Richter > Assignee: Snjezana Peco > > If I try to resize/maximize the JBDS window right after launch, it crashes when the window has not finished rendering before the resize. There is no error in the log, just Fedora telling me that the JVM crashed. Running with GTK2 doesn't produce this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3456) Resizing JBDS window right after is appears crashes it with GTK3

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3456?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3456: ------------------------------------ Assignee: Snjezana Peco > Resizing JBDS window right after is appears crashes it with GTK3 > ---------------------------------------------------------------- > > Key: JBDS-3456 > URL: https://issues.jboss.org/browse/JBDS-3456 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: ui/branding > Affects Versions: 9.0.0.Beta1 > Reporter: Jan Richter > Assignee: Snjezana Peco > > If I try to resize/maximize the JBDS window right after launch, it crashes when the window has not finished rendering before the resize. There is no error in the log, just Fedora telling me that the JVM crashed. Running with GTK2 doesn't produce this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3453) Launch after installation results in 'not responding' when running the installer on Java 7

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3453?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3453: ------------------------------------- Java stack trace could be also helpful: 1. jps -v 2. jstack ${java-pid} where java-pid is process ID from step 1. > Launch after installation results in 'not responding' when running the installer on Java 7 > ------------------------------------------------------------------------------------------ > > Key: JBDS-3453 > URL: https://issues.jboss.org/browse/JBDS-3453 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta1 > Environment: Fedora 20, 64-bit > installer run with OpenJDK 1.7.0_79 > devstudio run with OpenJDK 1.8.0_45 > Reporter: Jan Richter > Attachments: .log > > > When I try to launch JBDS from the installer, which I run with Java 7, after choosing a workspace (using a clean workspace btw.) the 'loading' splash disappears shortly after it shows up (and the progress bar is still somewhere around the beginning). > Then a blank JBDS window appears and about 10 - 20 seconds later a 'Not Responding' dialog appears followed by the rest of JBDS right away. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3453) Launch after installation results in 'not responding' when running the installer on Java 7

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3453?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3453: ------------------------------------- I had the same problem, but on Mac OS X. It feels like jvm has not enough memory. What amount of RAM do you have? > Launch after installation results in 'not responding' when running the installer on Java 7 > ------------------------------------------------------------------------------------------ > > Key: JBDS-3453 > URL: https://issues.jboss.org/browse/JBDS-3453 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta1 > Environment: Fedora 20, 64-bit > installer run with OpenJDK 1.7.0_79 > devstudio run with OpenJDK 1.8.0_45 > Reporter: Jan Richter > Attachments: .log > > > When I try to launch JBDS from the installer, which I run with Java 7, after choosing a workspace (using a clean workspace btw.) the 'loading' splash disappears shortly after it shows up (and the progress bar is still somewhere around the beginning). > Then a blank JBDS window appears and about 10 - 20 seconds later a 'Not Responding' dialog appears followed by the rest of JBDS right away. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3446) Add support for IzPack INSTALL_PATH property to predefine installation path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3446?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3446: ------------------------------------- This feature would compliment automated installer. It would be much easier to use than automated installer in case when everything should be done by default. There would be no need to have .xml file just "java -jar installer.jar -console". We should also add flag to accept license by default or it would stop and wait for input. > Add support for IzPack INSTALL_PATH property to predefine installation path > --------------------------------------------------------------------------- > > Key: JBDS-3446 > URL: https://issues.jboss.org/browse/JBDS-3446 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 8.1.0.GA > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > > In a recent discussion around JBIDE-19852 , it was pointed out that IzPack supports supplying properties to the installer, so that some values are predefined. > Details are here: > http://docs.codehaus.org/display/IZPACK/Unattended+Installations > The idea is that you could run this: > java -DINSTALL_PATH=/default/path -jar installer.jar > And this would pre-fill the installation path to the path given in the command. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19737) Add template info page after template list in create from app flow

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19737?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-19737. --------------------------------- Verified in JBDS 9.0.0.Beta1 build id B34. > Add template info page after template list in create from app flow > ------------------------------------------------------------------ > > Key: JBIDE-19737 > URL: https://issues.jboss.org/browse/JBIDE-19737 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > > Add a template info page that identifies key aspects of a template that a user has choosen so they can ensure they want to continue -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20004) OpenShift v3 resources names should be camelcasized or splitted by space character

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-20004: ------------------------------------- Summary: OpenShift v3 resources names should be camelcasized or splitted by space character Key: JBIDE-20004 URL: https://issues.jboss.org/browse/JBIDE-20004 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Marián Labuda Currently OpenShift v3 resources are as one long name and without camel case practice or spaces or spaces with capitalized first letters. It would be better to have more appropriate format. Affected resources: * Buildconfigs should be "Build configs" or "BuildConfigs" or "Build Configs" * Deploymentsconfigs should be "Deployment configs" or "DeploymentConfigs" or "Deployment Configs" * Imagestream should be "Image streams" or "ImageStreams" or "Image Streams" * Replicationcontrollers should be "Replication controllers" or "ReplicationControllers" or "Replication Controllers" I would suggest to use capitalized separated wording but I leave it up to decision of developer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 June 2015