[JBoss JIRA] (JBDS-2880) com.jboss.jbds.product.EclipseGenerator application failure in isntaller
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2880?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2880:
--------------------------------
Steps to Reproduce:
# EXEC: install JBDS studio to $\{target-folder\}
# ASSERT: There is no reported exception in log files created in ${target-folder}/studio/p2/director/configuration
was:
# EXEC: install JBDS studio to ${target-folder}
# ASSERT: There is no reported exception in log files created in ${target-folder}/studio/p2/director/configuration
> com.jboss.jbds.product.EclipseGenerator application failure in isntaller
> ------------------------------------------------------------------------
>
> Key: JBDS-2880
> URL: https://issues.jboss.org/browse/JBDS-2880
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 8.0.0.Alpha2
>
>
> {code}!SESSION 2014-01-16 16:34:55.784 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_51
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -application com.jboss.jbds.product.EclipseGenerator
> Command-line arguments: -application com.jboss.jbds.product.EclipseGenerator -clean
> !ENTRY org.eclipse.osgi 4 0 2014-01-16 16:34:57.716
> !MESSAGE Application error
> !STACK 1
> java.lang.RuntimeException: Application "com.jboss.jbds.product.EclipseGenerator" could not be found in the registry. The applications available are: com.jboss.jbds.p2.director, org.eclipse.equinox.app.error, org.eclipse.equinox.p2.director, org.eclipse.equinox.p2.garbagecollector.application, org.eclipse.equinox.p2.publisher.InstallPublisher, org.eclipse.equinox.p2.publisher.EclipseGenerator, org.eclipse.equinox.p2.publisher.ProductPublisher, org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher, org.eclipse.equinox.p2.repository.repo2runnable, org.eclipse.equinox.p2.repository.metadataverifier, org.eclipse.equinox.p2.artifact.repository.mirrorApplication, org.eclipse.equinox.p2.metadata.repository.mirrorApplication.
> at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:248)
> at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426){code}
> Installer could not run this application becasue it is trying to start it inside p2 director, just installed product should be used instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2880) com.jboss.jbds.product.EclipseGenerator application failure in isntaller
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2880?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-2880:
-------------------------------------
There are to options how to fix this issue:
1. Make generator actually run and initialize jbds so first start would be faster
2. Remove this step at all
> com.jboss.jbds.product.EclipseGenerator application failure in isntaller
> ------------------------------------------------------------------------
>
> Key: JBDS-2880
> URL: https://issues.jboss.org/browse/JBDS-2880
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 8.0.0.Alpha2
>
>
> {code}!SESSION 2014-01-16 16:34:55.784 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_51
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -application com.jboss.jbds.product.EclipseGenerator
> Command-line arguments: -application com.jboss.jbds.product.EclipseGenerator -clean
> !ENTRY org.eclipse.osgi 4 0 2014-01-16 16:34:57.716
> !MESSAGE Application error
> !STACK 1
> java.lang.RuntimeException: Application "com.jboss.jbds.product.EclipseGenerator" could not be found in the registry. The applications available are: com.jboss.jbds.p2.director, org.eclipse.equinox.app.error, org.eclipse.equinox.p2.director, org.eclipse.equinox.p2.garbagecollector.application, org.eclipse.equinox.p2.publisher.InstallPublisher, org.eclipse.equinox.p2.publisher.EclipseGenerator, org.eclipse.equinox.p2.publisher.ProductPublisher, org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher, org.eclipse.equinox.p2.repository.repo2runnable, org.eclipse.equinox.p2.repository.metadataverifier, org.eclipse.equinox.p2.artifact.repository.mirrorApplication, org.eclipse.equinox.p2.metadata.repository.mirrorApplication.
> at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:248)
> at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426){code}
> Installer could not run this application becasue it is trying to start it inside p2 director, just installed product should be used instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-3937) Create Stress JUnit Test Suite withch is included all available JUnit tests from all components
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3937?page=com.atlassian.jira.plugin... ]
Denis Golovin commented on JBIDE-3937:
--------------------------------------
{qoute}Ok. But a performance test must be "static", ie the content of the test mustn't change over time or it invalidates the time trend. So, if it's about performance test, it's necessary to have a dedicated test case or test suite that won't move with time. I don't think integration tests fit well.
I know [~vpakan] is currently working on setting up some performance tests for JBoss Tools.{quote}
I agree, so it just a suggestion for a stress test to see if fully loaded product survives through such rigorous eclipse session.
> Create Stress JUnit Test Suite withch is included all available JUnit tests from all components
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-3937
> URL: https://issues.jboss.org/browse/JBIDE-3937
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, qa
> Affects Versions: 3.0.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.2.x
>
>
> Why we need this?
> The Idea is in emulation a long development session. Now all tests suites are ran one by one each in its own session on clean workspace. A longest test suite takes around 15-20 minutes. Such test suite would emulate an about one hour long development session which can help to find memory leaks or other integration problems.
> It should be able to start on selected JBT build. It should download last or selected version of JBT form download site and start Stress Test Suite.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-2635:
-------------------------------------
My suggestion is about developing installer as RCP application without IzPack not implementing IzPack.
> Installation sometimes fail with bundle was not found on Windows
> ----------------------------------------------------------------
>
> Key: JBDS-2635
> URL: https://issues.jboss.org/browse/JBDS-2635
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.0.0.Beta1
> Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07
> Reporter: Jiri Peterka
> Assignee: Denis Golovin
> Fix For: 8.0.0.Alpha2
>
> Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log
>
>
> For the first time JBDS 7.0.0.Beta1 failed on windows8:
> {code}
> An error occurred while installing the items
> session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
> The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found.
> Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-2032) Help button works not in all wizards.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2032?page=com.atlassian.jira.plugin... ]
Denis Golovin commented on JBIDE-2032:
--------------------------------------
{quote}your PR is similar to what I thought. I would put it in foundation though and I'm wondering if there is a way to provide a more dynamic doc installation - one that link these to different docs based on what product are installed.{quote}
Do you want to have one help plug-in with default help context that would be referenced everywhere and show links to different docs based on what is installed JBT or JBDS?
Help context is extendable, if plug-in extend help context it can:
1. Override context's text (text between title and 'See Also' list)
2. Add Links to See Also list
It could be default help context with text about JBT and link to JBoss Tools Guides. When JBDS is installed it can override text with JBDS related content and and link to JBDS Guides.
> Help button works not in all wizards.
> -------------------------------------
>
> Key: JBIDE-2032
> URL: https://issues.jboss.org/browse/JBIDE-2032
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: help
> Affects Versions: 2.1.0.beta1
> Reporter: Anton Klimkovich
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: CreateJSFLibrary.PNG, DriverDefinitions.PNG, EditDriverDefinitions.PNG, InstallNewServerAdapter.PNG, JSFImplementationLibrary.PNG, NewConnectionProfile.PNG, NewDriverDefinitions.PNG, NewSeamRuntime.PNG, NewServer.PNG, Resource - Eclipse Platform _028.png
>
>
> Wizards with non-working help button attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16396) Generate new content in New Footer wizard for JQM 1.4
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16396?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-16396:
------------------------------------------
Description:
1. Difference from JQM 1.3:
Buttons should be set with classes
{code}
<a href="#" class="ui-btn ui-btn-icon-right ui-icon-plus">Add</a>
{code}
2. Enhancement:
Already in JQM 1.3 controlgroup can be positioned left or right to the title by adding class 'ui-btn-left' or 'ui-btn-right' so that new input control can be added to the wizard
{code}
Bar position: o Default o Left o Right
{code}
enabled when input 'Arrangement' is set to 'Grouped'.
Default positioning is provided by flow layout, in which title and buttons are placed to different lines, which is implemented in wizard at present. For navbar, attempts to put it left or right result in poor layout.
was:
1. Difference from JQM 1.3:
When buttons are provided by links as direct children or in controlgroup widget, they should be set with classes
{code}
<a href="#" class="ui-btn ui-btn-icon-right ui-icon-plus">Add</a>
{code}
(but links in navbar widget should be left the same as in JQM 1.3).
2. Enhancement:
Already in JQM 1.3 controlgroup and navbar can be positioned left or right to the title by adding class 'ui-btn-left' or 'ui-btn-right' so that new input control can be added to the wizard
{code}
Bar position: o Default o Left o Right
{code}
enabled when input 'Arrangement' is set either to 'Grouped' or 'Navbar'.
Default positioning is provided by flow layout, in which title and buttons are placed to different lines, which is implemented in wizard at present.
> Generate new content in New Footer wizard for JQM 1.4
> -----------------------------------------------------
>
> Key: JBIDE-16396
> URL: https://issues.jboss.org/browse/JBIDE-16396
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha2
>
>
> 1. Difference from JQM 1.3:
> Buttons should be set with classes
> {code}
> <a href="#" class="ui-btn ui-btn-icon-right ui-icon-plus">Add</a>
> {code}
> 2. Enhancement:
> Already in JQM 1.3 controlgroup can be positioned left or right to the title by adding class 'ui-btn-left' or 'ui-btn-right' so that new input control can be added to the wizard
> {code}
> Bar position: o Default o Left o Right
> {code}
> enabled when input 'Arrangement' is set to 'Grouped'.
> Default positioning is provided by flow layout, in which title and buttons are placed to different lines, which is implemented in wizard at present. For navbar, attempts to put it left or right result in poor layout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16396) Generate new content in New Footer wizard for JQM 1.4
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16396?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-16396:
------------------------------------------
Description:
1. Difference from JQM 1.3:
When buttons are provided by links as direct children or in controlgroup widget, they should be set with classes
{code}
<a href="#" class="ui-btn ui-btn-icon-right ui-icon-plus">Add</a>
{code}
(but links in navbar widget should be left the same as in JQM 1.3).
2. Enhancement:
Already in JQM 1.3 controlgroup and navbar can be positioned left or right to the title by adding class 'ui-btn-left' or 'ui-btn-right' so that new input control can be added to the wizard
{code}
Bar position: o Default o Left o Right
{code}
enabled when input 'Arrangement' is set either to 'Grouped' or 'Navbar'.
Default positioning is provided by flow layout, in which title and buttons are placed to different lines, which is implemented in wizard at present.
was:
Changes from JQM 1.3:
1. When buttons are provided by links as direct children or in controlgroup widget, they should be set with classes
{code}
<a href="#" class="ui-btn ui-btn-icon-right ui-icon-plus">Add</a>
{code}
(but links in navbar widget should be left the same as in JQM 1.3).
2. Controlgroup and navbar can be positioned left or right to the title by adding class 'ui-btn-left' or 'ui-btn-right' so that new input control can be added to the wizard
{code}
Bar position: o Default o Left o Right
{code}
enabled when input 'Arrangement' is set either to 'Grouped' or 'Navbar'.
> Generate new content in New Footer wizard for JQM 1.4
> -----------------------------------------------------
>
> Key: JBIDE-16396
> URL: https://issues.jboss.org/browse/JBIDE-16396
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha2
>
>
> 1. Difference from JQM 1.3:
> When buttons are provided by links as direct children or in controlgroup widget, they should be set with classes
> {code}
> <a href="#" class="ui-btn ui-btn-icon-right ui-icon-plus">Add</a>
> {code}
> (but links in navbar widget should be left the same as in JQM 1.3).
> 2. Enhancement:
> Already in JQM 1.3 controlgroup and navbar can be positioned left or right to the title by adding class 'ui-btn-left' or 'ui-btn-right' so that new input control can be added to the wizard
> {code}
> Bar position: o Default o Left o Right
> {code}
> enabled when input 'Arrangement' is set either to 'Grouped' or 'Navbar'.
> Default positioning is provided by flow layout, in which title and buttons are placed to different lines, which is implemented in wizard at present.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16396) Generate new content in New Footer wizard for JQM 1.4
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16396?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-16396:
------------------------------------------
Description:
Changes from JQM 1.3:
1. When buttons are provided by links as direct children or in controlgroup widget, they should be set with classes
{code}
<a href="#" class="ui-btn ui-btn-icon-right ui-icon-plus">Add</a>
{code}
(but links in navbar widget should be left the same as in JQM 1.3).
2. Controlgroup and navbar can be positioned left or right to the title by adding class 'ui-btn-left' or 'ui-btn-right' so that new input control can be added to the wizard
{code}
Bar position: o Default o Left o Right
{code}
enabled when input 'Arrangement' is set either to 'Grouped' or 'Navbar'.
was:
Changes from JQM 1.3:
1. When buttons are provided by links as direct children or in controlgroup widget, they should be set with classes
{code}
<a href="#" class="ui-btn ui-btn-icon-right ui-icon-plus">Add</a>
{code}
2. Controlgroup and navbar can be positioned left or right to the title by adding class 'ui-btn-left' or 'ui-btn-right' so that new input control can be added to the wizard
{code}
Bar position: o Default o Left o Right
{code}
enabled when input 'Arrangement' is set either to 'Grouped' or 'Navbar'.
> Generate new content in New Footer wizard for JQM 1.4
> -----------------------------------------------------
>
> Key: JBIDE-16396
> URL: https://issues.jboss.org/browse/JBIDE-16396
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha2
>
>
> Changes from JQM 1.3:
> 1. When buttons are provided by links as direct children or in controlgroup widget, they should be set with classes
> {code}
> <a href="#" class="ui-btn ui-btn-icon-right ui-icon-plus">Add</a>
> {code}
> (but links in navbar widget should be left the same as in JQM 1.3).
> 2. Controlgroup and navbar can be positioned left or right to the title by adding class 'ui-btn-left' or 'ui-btn-right' so that new input control can be added to the wizard
> {code}
> Bar position: o Default o Left o Right
> {code}
> enabled when input 'Arrangement' is set either to 'Grouped' or 'Navbar'.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16396) Generate new content in New Footer wizard for JQM 1.4
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-16396:
---------------------------------------------
Summary: Generate new content in New Footer wizard for JQM 1.4
Key: JBIDE-16396
URL: https://issues.jboss.org/browse/JBIDE-16396
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsp/jsf/xml/html source editing
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.2.0.Alpha2
Changes from JQM 1.3:
1. When buttons are provided by links as direct children or in controlgroup widget, they should be set with classes
{code}
<a href="#" class="ui-btn ui-btn-icon-right ui-icon-plus">Add</a>
{code}
2. Controlgroup and navbar can be positioned left or right to the title by adding class 'ui-btn-left' or 'ui-btn-right' so that new input control can be added to the wizard
{code}
Bar position: o Default o Left o Right
{code}
enabled when input 'Arrangement' is set either to 'Grouped' or 'Navbar'.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2492) JBDS Icon problems in Gnome 3.6 Application Switcher
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2492?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2492:
--------------------------------
Attachment: appnamexfce.png
Name problem is still present in Luna see attached [^appnamexfce.png] but resolution problem seems to be fixed.
> JBDS Icon problems in Gnome 3.6 Application Switcher
> ----------------------------------------------------
>
> Key: JBDS-2492
> URL: https://issues.jboss.org/browse/JBDS-2492
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: ui/branding
> Affects Versions: 6.0.1.GA
> Environment: Ubuntu Linux x86_64
> Gnome 3.6.0
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 8.0.0.Alpha2
>
> Attachments: app-switcher.png, appnamexfce.png
>
>
> Problems are:
> # Icon Resolution is to low
> # No application name under icon
> !app-switcher.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months