[JBoss JIRA] (JBIDE-21611) Reduce bloat in CDK server adapter menus
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21611?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21611:
--------------------------------
Description:
The CDK server adapter menus display a lot of useless/disabled menus:
!cdk-server-menus.png!
It'd be nice to clean that up. Keep
-(re)start
-stop
-Show in> OpenShift, Docker
-Delete
-rename
-properties
It reckon it might not be possible to get rid of all the cruft (when menus are defined upstream), but we might be able to clean som of the stuff menus we "own".
was:
The CDK server adapter menus display a lot of useless/disabled menus:
!cdk-servers-menus.png!
It'd be nice to clean that up. Keep
-(re)start
-stop
-Show in> OpenShift, Docker
-Delete
-rename
-properties
It reckon it might not be possible to get rid of all the cruft (when menus are defined upstream), but we might be able to clean som of the stuff menus we "own".
> Reduce bloat in CDK server adapter menus
> ----------------------------------------
>
> Key: JBIDE-21611
> URL: https://issues.jboss.org/browse/JBIDE-21611
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Priority: Minor
> Attachments: cdk-server-menus.png
>
>
> The CDK server adapter menus display a lot of useless/disabled menus:
> !cdk-server-menus.png!
> It'd be nice to clean that up. Keep
> -(re)start
> -stop
> -Show in> OpenShift, Docker
> -Delete
> -rename
> -properties
> It reckon it might not be possible to get rid of all the cruft (when menus are defined upstream), but we might be able to clean som of the stuff menus we "own".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBDS-2260) Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only)
by Surender Dalal (JIRA)
[ https://issues.jboss.org/browse/JBDS-2260?page=com.atlassian.jira.plugin.... ]
Surender Dalal edited comment on JBDS-2260 at 1/28/16 4:56 PM:
---------------------------------------------------------------
Open command as Run Administrator and go to where your studio jar file
Now use below command.
java -Djava.io.tmpdir=c:/temp -DTRACE=TRUE -jar jboss-devstudio-9.0.0.GA-installer-eap.jar
was (Author: surendermca04):
Open command as Run Administrator and go to where your studio jar file
Now use below command and you can change you jar file name:
java -Djava.io.tmpdir=c:/temp -DTRACE=TRUE -jar jboss-devstudio-9.0.0.GA-installer-eap.jar
> Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only)
> ------------------------------------------------------------------------------------------------
>
> Key: JBDS-2260
> URL: https://issues.jboss.org/browse/JBDS-2260
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 5.0.0.GA
> Reporter: Isaac Rooskov
> Assignee: Denis Golovin
> Fix For: LATER
>
> Attachments: JavaVersionReader.java.patch
>
>
> *From customer in Bugzilla*
> Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=850793
> Description of issue from customer:
> Description of problem:
> Installation of JBoss Developer Studion 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4
> Version-Release number of selected component (if applicable):
> JBOSS Developer Studio 5.0.0.GA
> How reproducible:
> Start installation using
> java - jar jbdevstudio-product-universal-5.0.0.v20120615-1714-H213-GA.jar
> Actual results:
> Installation is not passing at step 7 of 9, progress 1 of 4.
> Expected results:
> Additional info:
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBDS-2260) Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only)
by Surender Dalal (JIRA)
[ https://issues.jboss.org/browse/JBDS-2260?page=com.atlassian.jira.plugin.... ]
Surender Dalal commented on JBDS-2260:
--------------------------------------
Open command as Run Administrator and go to where your studio jar file
Now use below command and you can change you jar file name:
java -Djava.io.tmpdir=c:/temp -DTRACE=TRUE -jar jboss-devstudio-9.0.0.GA-installer-eap.jar
> Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only)
> ------------------------------------------------------------------------------------------------
>
> Key: JBDS-2260
> URL: https://issues.jboss.org/browse/JBDS-2260
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 5.0.0.GA
> Reporter: Isaac Rooskov
> Assignee: Denis Golovin
> Fix For: LATER
>
> Attachments: JavaVersionReader.java.patch
>
>
> *From customer in Bugzilla*
> Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=850793
> Description of issue from customer:
> Description of problem:
> Installation of JBoss Developer Studion 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4
> Version-Release number of selected component (if applicable):
> JBOSS Developer Studio 5.0.0.GA
> How reproducible:
> Start installation using
> java - jar jbdevstudio-product-universal-5.0.0.v20120615-1714-H213-GA.jar
> Actual results:
> Installation is not passing at step 7 of 9, progress 1 of 4.
> Expected results:
> Additional info:
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21529) Properties view: Columns of OpenShift resources in tabbed properties are too wide
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21529?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21529:
-------------------------------------
It doesn't seem to make a difference. There are still outstanding column sizing issues
> Properties view: Columns of OpenShift resources in tabbed properties are too wide
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-21529
> URL: https://issues.jboss.org/browse/JBIDE-21529
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Labels: properties
> Fix For: 4.3.1.CR1
>
>
> In new tabbed properties overview of OpenShift resources there is a table listing selected OpenShift resource, e.g. pods, builds etc. Columns in this table are too wide by default and their width exceed few times content of the column. It makes necessary to scroll or resize columns, what make it less user friendly. Columns could fit more to length of content of the column by default.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21589) JBDS crash sometimes when opening Show in Console on a project
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21589?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21589 at 1/28/16 3:55 PM:
-------------------------------------------------------------------
[~mlabuda]I cant reproduce this (I have fc23, gtk3-3.18.6-1.fc23.x86_64, webkitgtk-2.4.9-3.fc23.x86_64, webkitgtk3-2.4.9-3.fc23.x86_64).
This very much looks like the webkit problem there is in Eclipse/GTK3, which crashes Eclipse. I see the following in the stack:
{code}
J 26556 C1 org.eclipse.swt.browser.WebKit.webkit_notify_progress(JJ)J (118 bytes) @ 0x00007f0dd1118bc4 [0x00007f0dd1118320+0x8a4]
{code}
It can be reproduced if you open the internal browser, open the javadoc view or code autocompletion (and other cases I am not aware of).
It happens in GTK3 system which have chrome and google talk/bluejeans installed.
It should not happen any more if you either:
* disable GTK3: export SWT_GTK3=0 in console before launching Eclipse
* switch the internal browser to firefox
* add -Dorg.eclipse.swt.browser.DefaultType=mozilla to your eclipse.ini
* ...
Can try this, please? If this helps, then this clearly is the good old webkit segfault issue.
The Eclipse bugzillas are here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=334466
was (Author: adietish):
[~mlabuda]I cant reproduce this but this very much looks like the webkit problem there is in GTK3, which crashes Eclipse. I see the following in the stack:
{code}
J 26556 C1 org.eclipse.swt.browser.WebKit.webkit_notify_progress(JJ)J (118 bytes) @ 0x00007f0dd1118bc4 [0x00007f0dd1118320+0x8a4]
{code}
It can be reproduced if you open the internal browser, open the javadoc view or code autocompletion (and other cases I am not aware of).
It happens in GTK3 system which have google talk or bluejeans plugin installed.
It should not happen any more if you either:
* disable GTK3: export SWT_GTK3=0 in console before launching Eclipse
* switch the internal browser to firefox
* add -Dorg.eclipse.swt.browser.DefaultType=mozilla to your eclipse.ini
* ...
Can try this, please?
The Eclipse bugzillas are here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=334466
> JBDS crash sometimes when opening Show in Console on a project
> --------------------------------------------------------------
>
> Key: JBIDE-21589
> URL: https://issues.jboss.org/browse/JBIDE-21589
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: Fedora 22
> openjdk 8.0_71-b15
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3
> Attachments: log.txt
>
>
> Crash log
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007f0cfe0bbcaf, pid=13526, tid=139697620236032
> #
> # JRE version: OpenJDK Runtime Environment (8.0_71-b15) (build 1.8.0_71-b15)
> # Java VM: OpenJDK 64-Bit Server VM (25.71-b15 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libwebkitgtk-3.0.so.0+0x47bcaf]
> #
> # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # /home/mlabuda/testing/jbds/910Beta2stable/hs_err_pid13526.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> {code}
> For more thread dump see attached log.txt
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21589) JBDS crash sometimes when opening Show in Console on a project
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21589?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21589 at 1/28/16 3:35 PM:
-------------------------------------------------------------------
[~mlabuda]I cant reproduce this but this very much looks like the webkit problem there is in GTK3, which crashes Eclipse. I see the following in the stack:
{code}
J 26556 C1 org.eclipse.swt.browser.WebKit.webkit_notify_progress(JJ)J (118 bytes) @ 0x00007f0dd1118bc4 [0x00007f0dd1118320+0x8a4]
{code}
It can be reproduced if you open the internal browser, open the javadoc view or code autocompletion (and other cases I am not aware of).
It happens in GTK3 system which have google talk or bluejeans plugin installed.
It should not happen any more if you either:
* disable GTK3: export SWT_GTK3=0 in console before launching Eclipse
* switch the internal browser to firefox
* add -Dorg.eclipse.swt.browser.DefaultType=mozilla to your eclipse.ini
* ...
Can try this, please?
The Eclipse bugzillas are here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=334466
was (Author: adietish):
[~mlabuda]I cant reproduce this but this very much looks like the webkit problem there is in GTK3, which crashes Eclipse. It can be reproduced if you open the internal browser, open the javadoc view or code autocompletion (and other cases I am not aware of).
It happens in GTK3 system which have google talk or bluejeans plugin installed.
It should not happen any more if you either:
* disable GTK3: export SWT_GTK3=0 in console before launching Eclipse
* switch the internal browser to firefox
* add -Dorg.eclipse.swt.browser.DefaultType=mozilla to your eclipse.ini
* ...
Can try this, please?
I see the following in the stack:
{code}
J 26556 C1 org.eclipse.swt.browser.WebKit.webkit_notify_progress(JJ)J (118 bytes) @ 0x00007f0dd1118bc4 [0x00007f0dd1118320+0x8a4]
{code}
The Eclipse bugzillas are here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=334466
> JBDS crash sometimes when opening Show in Console on a project
> --------------------------------------------------------------
>
> Key: JBIDE-21589
> URL: https://issues.jboss.org/browse/JBIDE-21589
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: Fedora 22
> openjdk 8.0_71-b15
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3
> Attachments: log.txt
>
>
> Crash log
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007f0cfe0bbcaf, pid=13526, tid=139697620236032
> #
> # JRE version: OpenJDK Runtime Environment (8.0_71-b15) (build 1.8.0_71-b15)
> # Java VM: OpenJDK 64-Bit Server VM (25.71-b15 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libwebkitgtk-3.0.so.0+0x47bcaf]
> #
> # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # /home/mlabuda/testing/jbds/910Beta2stable/hs_err_pid13526.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> {code}
> For more thread dump see attached log.txt
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21589) JBDS crash sometimes when opening Show in Console on a project
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21589?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21589 at 1/28/16 3:35 PM:
-------------------------------------------------------------------
[~mlabuda]I cant reproduce this but this very much looks like the webkit problem there is in GTK3, which crashes Eclipse. I see the following in the stack:
{code}
J 26556 C1 org.eclipse.swt.browser.WebKit.webkit_notify_progress(JJ)J (118 bytes) @ 0x00007f0dd1118bc4 [0x00007f0dd1118320+0x8a4]
{code}
It can be reproduced if you open the internal browser, open the javadoc view or code autocompletion (and other cases I am not aware of).
It happens in GTK3 system which have google talk or bluejeans plugin installed.
It should not happen any more if you either:
* disable GTK3: export SWT_GTK3=0 in console before launching Eclipse
* switch the internal browser to firefox
* add -Dorg.eclipse.swt.browser.DefaultType=mozilla to your eclipse.ini
* ...
Can try this, please?
The Eclipse bugzillas are here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=334466
was (Author: adietish):
[~mlabuda]I cant reproduce this but this very much looks like the webkit problem there is in GTK3, which crashes Eclipse. I see the following in the stack:
{code}
J 26556 C1 org.eclipse.swt.browser.WebKit.webkit_notify_progress(JJ)J (118 bytes) @ 0x00007f0dd1118bc4 [0x00007f0dd1118320+0x8a4]
{code}
It can be reproduced if you open the internal browser, open the javadoc view or code autocompletion (and other cases I am not aware of).
It happens in GTK3 system which have google talk or bluejeans plugin installed.
It should not happen any more if you either:
* disable GTK3: export SWT_GTK3=0 in console before launching Eclipse
* switch the internal browser to firefox
* add -Dorg.eclipse.swt.browser.DefaultType=mozilla to your eclipse.ini
* ...
Can try this, please?
The Eclipse bugzillas are here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=334466
> JBDS crash sometimes when opening Show in Console on a project
> --------------------------------------------------------------
>
> Key: JBIDE-21589
> URL: https://issues.jboss.org/browse/JBIDE-21589
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: Fedora 22
> openjdk 8.0_71-b15
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3
> Attachments: log.txt
>
>
> Crash log
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007f0cfe0bbcaf, pid=13526, tid=139697620236032
> #
> # JRE version: OpenJDK Runtime Environment (8.0_71-b15) (build 1.8.0_71-b15)
> # Java VM: OpenJDK 64-Bit Server VM (25.71-b15 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libwebkitgtk-3.0.so.0+0x47bcaf]
> #
> # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # /home/mlabuda/testing/jbds/910Beta2stable/hs_err_pid13526.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> {code}
> For more thread dump see attached log.txt
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBDS-3585) Update support matrix to include OS X El Capitan (10.11)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3585?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-3585:
------------------------------------
Assignee: Martin Malina
> Update support matrix to include OS X El Capitan (10.11)
> --------------------------------------------------------
>
> Key: JBDS-3585
> URL: https://issues.jboss.org/browse/JBDS-3585
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: requirements
> Affects Versions: 9.1.0.Beta1
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 9.1.0.Beta2
>
>
> OS X El Capitan 10.11 was released in autumn 2015 and we actually tested JBDS 9.0 with it already, but it was too late to change the support matrix. So let's do it for JBDS 9.1.
> I suggest to have the latest two versions for JBDS 9.1, i.e. Yosemite and El Capitan.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months