[
https://issues.jboss.org/browse/JBIDE-13990?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-13990 at 4/11/13 11:50 AM:
--------------------------------------------------------------
On Fedora 18 [uname -a ==> 'Linux thunk 3.8.2-206.fc18.x86_64 #1 SMP Fri Mar 8
15:03:34 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux'].
With
http://whatsmyuseragent.com/, I get the follow values for Firefox and Chrome:
* Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0
* Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.22 (KHTML, like Gecko)
Chrome/25.0.1364.172 Safari/537.22
PR for master:
https://github.com/jbosstools/jbosstools-base/pull/80 (could be applied in
other 4.0.x/4.1.0.Alpha2 branches too, if desired).
was (Author: nickboldt):
On Fedora 18, using
http://whatsmyuseragent.com/, I get the follow values for Firefox
and Chrome:
* Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0
* Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.22 (KHTML, like Gecko)
Chrome/25.0.1364.172 Safari/537.22
PR for master:
https://github.com/jbosstools/jbosstools-base/pull/80 (could be applied in
other 4.0.x/4.1.0.Alpha2 branches too, if desired).
Linux usage stats hardcoded to x86 so no data collected for x86_64
------------------------------------------------------------------
Key: JBIDE-13990
URL:
https://issues.jboss.org/browse/JBIDE-13990
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: usage
Affects Versions: 4.0.1.Final, 4.1.0.Alpha2
Reporter: Nick Boldt
Assignee: Andre Dietisheim
[~maxandersen] found this bug today when looking at why we have no 64-bit Linux usage
data:
{code:title=https://github.com/jbosstools/jbosstools-base/blob/master/usage/plugins/org.jboss.tools.usage/src/org/jboss/tools/usage/googleanalytics/eclipse/EclipseUserAgent.java#L35}
private static final String USERAGENT_LINUX = "{0}/{1} (X11; U; Linux i686;
{3})"; //$NON-NLS-1$
{code}
Suggestion: we should replace i686 with \{2\}.
--
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