[JBoss JIRA] (JBIDE-16861) Shade of blue text in JBoss Central 'Getting Started' tab changed
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16861?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-16861.
---------------------------------
Assignee: Fred Bricon
Fix Version/s: 4.2.0.Beta2
(was: 4.2.x)
Resolution: Done
There, using a lighter blue (#EDF5FE) for the highlit background :
!http://content.screencast.com/users/fbricon/folders/Jing/media/9a1b76bc-0d10-45c2-96fa-29ca0befb701/lighter-blue.png!
I can't test w/ GTK3 right now, you'll have to wait for a nightly build to see how it looks with Fedora.
> Shade of blue text in JBoss Central 'Getting Started' tab changed
> -----------------------------------------------------------------
>
> Key: JBIDE-16861
> URL: https://issues.jboss.org/browse/JBIDE-16861
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta1
> Environment: Fedora 19, 64-bit, java version "1.7.0_51", OpenJDK Runtime Environment (fedora-2.4.5.0.fc19-x86_64 u51-b31)
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Priority: Minor
> Labels: gtk3, upstream
> Fix For: 4.2.0.Beta2
>
> Attachments: Central_fontcolor_711.png, Central_fontcolor_800B1.png
>
>
> Text in JBoss Central 'Getting Started' tab is now light blue instead of the darker blue in 7.1.1. This change makes it harder to read the text when there is also a blue shaded background. Was this change intentional?
> *7.1.1*
> !Central_fontcolor_711.png!
> *8.0.0.Beta1*
> !Central_fontcolor_800B1.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
11 years, 11 months
[JBoss JIRA] (JBIDE-17202) Importing/building WildFly 8.0.Final into JBTools 4.2.0.Beta1 results in GC faillure with Java 1.7.0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17202?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-17202:
-------------------------------
Summary: Importing/building WildFly 8.0.Final into JBTools 4.2.0.Beta1 results in GC faillure with Java 1.7.0 (was: Importing/building WildFly 8.0.Final into JBTools 4.2.0.Beta1 results in GC faillure with Java 1.0)
> Importing/building WildFly 8.0.Final into JBTools 4.2.0.Beta1 results in GC faillure with Java 1.7.0
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17202
> URL: https://issues.jboss.org/browse/JBIDE-17202
> Project: Tools (JBoss Tools)
> Issue Type: Quality Risk
> Components: build
> Affects Versions: 4.2.0.Beta1
> Environment: Linux 2.6.32-358.23.2.el6.x86_64 #1 SMP Sat Sep 14 05:32:37 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux
> java -version
> java version "1.7.0_25"
> OpenJDK Runtime Environment (rhel-2.3.10.4.el6_4-x86_64)
> OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
> Reporter: Len DiMaggio
> Attachments: log, Screenshot-1.png, Screenshot-2.png, Screenshot.png
>
>
> See attached logs and screenshots - building WildFly causes a GC failure
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-17202) Importing/building WildFly 8.0.Final into JBTools 4.2.0.Beta1 results in GC faillure with Java 1.0
by Len DiMaggio (JIRA)
Len DiMaggio created JBIDE-17202:
------------------------------------
Summary: Importing/building WildFly 8.0.Final into JBTools 4.2.0.Beta1 results in GC faillure with Java 1.0
Key: JBIDE-17202
URL: https://issues.jboss.org/browse/JBIDE-17202
Project: Tools (JBoss Tools)
Issue Type: Quality Risk
Components: build
Affects Versions: 4.2.0.Beta1
Environment: Linux 2.6.32-358.23.2.el6.x86_64 #1 SMP Sat Sep 14 05:32:37 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux
java -version
java version "1.7.0_25"
OpenJDK Runtime Environment (rhel-2.3.10.4.el6_4-x86_64)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
Reporter: Len DiMaggio
See attached logs and screenshots - building WildFly causes a GC failure
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-14971) PMD4 - Generate Abstract Syntax Tree fails
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14971?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-14971 at 4/27/14 9:35 PM:
-------------------------------------------------------------
Note that PMD 4.0.2 was already cleared by QE for inclusion in Central in JBDS 8.0.0.Beta1 (see JBDS-2969), but if we need to update that to 4.0.4.v20140427-0935 or later, we can do that.
was (Author: nickboldt):
Note that PMD 4.0.2 was already cleared by QE for inclusion in Central in JBDS 8.0.0.Beta1 (see JBDS-2969), but if we need to update that to 4.0.3 or later, we can do that.
> PMD4 - Generate Abstract Syntax Tree fails
> ------------------------------------------
>
> Key: JBIDE-14971
> URL: https://issues.jboss.org/browse/JBIDE-14971
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 4.1.0.Beta2
> Environment: java version "1.7.0_09-icedtea"
> OpenJDK Runtime Environment (rhel-2.3.3.2.el6_3-x86_64)
> OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)
> RHEL6
> Version: 7.0.0.Beta2
> Build id: Beta2-v20130616-1738-B261
> Build date: 20130616-1738
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Fix For: 4.2.0.Beta2
>
> Attachments: log.1, Screenshot.png
>
>
> Installed PMD4 from here:
> PMD - http://download.jboss.org/jbosstools/updates/requirements/pmd/4.0.0.v2013...
> Then selected source code and executed Generate Abstract Syntax Tree
> And hit this error:
> net.sourceforge.pmd.lang.java.ast.ParseException: Can't use static imports when running in JDK 1.4 mode!
--
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
11 years, 11 months