[
https://issues.jboss.org/browse/JBIDE-14016?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-14016:
------------------------------------
http://wiki.eclipse.org/Equinox_p2_download_stats states that you can manually set values
of OS/package/version/foo/bar/baz as you'd like, but querystring values appended to
the end of the HEAD request URL are the same as path segments... and since our installer
is universal (no platform specifics), and our update sites are similarly not platform
specific, I don't see how we can pass in anything meaningful here. For the case of
installed platform-specific fragments (eg., XulRunner) we can tell which OS is used
because the fragment will state as much (x86, x86_64, macosx, cocoa, win32, gtk, linux).
So... any suggestions for which IUs to track, if not ALL of them?
p2 download stats should only track a subset of features, with better
context than feature name
-----------------------------------------------------------------------------------------------
Key: JBIDE-14016
URL:
https://issues.jboss.org/browse/JBIDE-14016
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: updatesite
Affects Versions: 4.1.0.Alpha2
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Fix For: 4.1.0.Alpha2
[~maxandersen] said:
{quote}
We shouldn't track every feature - should review the list and also try add some more
context than just the feature name if possible.
{quote}
Questions to discuss in order to flesh out this request:
a) if not all, then which features? Where do we get the list? Do we need to parse the JBT
aggregate site's category.xml and pull out all features from a particular category,
such as the Core (Abridged) category?
b) what context do you want 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