Subject: [cross-project-issues-dev] p2 download stats ... again
just a couple of
things that I learned enabling my download stats - for more details
1. It is better to
tie stats to a FEATURE rarther than a bundle. Because bundles
in 2 variants (.pack.gz / .jar) so with a bundle you have duplicate work adding
stats tracker (and, the app from bug 310132 which auto-generates stats
ÂÂÂÂdoesn't support it).
1a) Note though that
a commercial product which uses a different feature
structure than Eclipse Open Source (and so just gets your bundle)
be counted when you count feature access. That's likely not
2. If you have a
feature and bundle with the same ID, don't add the
ÂÂÂproperty to both. Since it would count each download
3. It may be
adviseable to version your stats ID somehow. For instance,
"org.eclipse.rse.core_tm320" or "org.eclipse.wst.ui_helios_sr0"
"org.eclipse.ptp_4.0". If you dont' version the stats ID you are
you may run into troubles when we do Helios SR1 which will re-use
same repo location (/releases/helios).
4. Maybe obvious.
the stats tracker will not catch people updating from Galileo
Helios. Because the Galileo p2 impl did not have the stats code enabled.
only count p2 downloads that happen with Eclipse 3.6.
Â5. I'm wondering whether the helios aggregator's
access to my project
repository already counts as a download? Probably not too
So... if I just
confused hell out of you, best forget what I just wrote. In
end, as has been
stated before, download stats are only good for trends
and not for absolute
numbers anyways. So it's not worth putting too much
I'd hope though that
some of you found this helpful :)
MartinÂOberhuber, Senior Member of Technical
Staff, Wind River