Re: [cross-project-issues-dev] Download stats for p2

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

Adding an indicator of the repository
source should be fine. It means a little bit of extra work to collate the
statistics to find out the total download count, but if you really want
to know what repository downloads are coming from, I don't see why not.

David M Williams <david_williams@xxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

05/19/2010 10:50 PM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Subject	Re: [cross-project-issues-dev] Download stats for p2

doh. Of course. Thanks for the clarification on 'feature'. 

One more question/recommendation ... 

I think we should, by convention, add the "repo uri" to the repo
specific part? 

http://download.eclipse.org/stats</repo/uri>

so for example ... we'd have 

http://download.eclipse.org/stats/releases/helios

for the common repo ... but could use 

http://download.eclipse.org/stats/webtools/repository

for webtools specific artifact repositories. 

It would be the same amount of data coming back to eclipse.org, but would
help tell which 
repositories were in use ... in those cases where things are available
in multiple repos. 

Make sense? Any reason not to? 

Thanks again.

From:	John Arthorne <John_Arthorne@xxxxxxxxxx>
To:	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:	05/19/2010 10:29 PM
Subject:	Re: [cross-project-issues-dev] Download stats for p2
Sent by:	cross-project-issues-dev-bounces@xxxxxxxxxxx

---

David Williams wrote on 05/19/2010 03:11:49 PM:
> The more technical question, the directions say,  "You can
pick one 
> plugin in your feature for example " 
> Does it have to be a plugin? Could it not be the "...feature.group"?
> Was there a reason the instructions say "plugin"? For example,
is 
> there a trick to include a "tracking plugin" in a feature?

The "..feature.group" is in the metadata but is not an artifact
(something that is downloaded during install). There is an artifact containing
the feature.xml file that could be used though.  Feature artifacts
something like this: 

   <artifact classifier='org.eclipse.update.feature' id='org.eclipse.sdk'
version='...' 


The stats mechanism works the same on any artifact. So, you could use the
artifact for either a feature or plugin with the same effect.

John_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev