Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cross-project-issues-dev] Download stats for p2

> ... most users will choose Helios repo to install features and can we track that? Will someone add the track properties to the metadata of Helios repo?

Yes, I'll add following property to the helios artifacts repo. (I prefer the "full" '/releases/helios' if that doesn't cause problems).
<property name='p2.statsURI' value=''/>

Any 'download.stats' properties from your artifact repository should be copied over to the common one.
I do not see any 'download.stats'properties in the current RC1 repo, however. Did you have some in your
contribution to RC1? If so, sounds like we have a bug (or, I misunderstand). If not, and you are just experimenting
with your next contribution, then we'll test it from common repo next week.


From: "Xiaoying Gu" <xgu@xxxxxxxxxxx>
To: "Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx>
Date: 05/21/2010 03:33 AM
Subject: RE: [cross-project-issues-dev] Download stats for p2
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

I tried this on BIRT 2.6 repository. I used the URL: in artifacts.jar
After installing BIRT from this repository, I checked Download Stats in committer tool and found there is counts for the bundle?
Does the download stats updated immediately  according the http request?
Another question, when Helios is released, most users will choose Helios repo to install features and can we track that? Will someone add the track properties to the metadata of Helios repo?
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Denis Roy
520 23:51
Cross project issues
Re: [cross-project-issues-dev] Download stats for p2

You could actually have it easy both ways.

When using the Download Stats UI, searching for "somejar-versionid" will return both URLs, and can be grouped into a single result.  Obviously, searching for /stats/webtools/somejar-versionid will return only those results in the webtools directory.

BTW: no need to pollute the URL with "/releases" unless you're keen on maintaining consistency with the location of the file on  /helios/somejar should work, and will still allow you to separate the two service releases, /helios/sr1/somejar and /helios/sr2/somejar.


On 05/19/2010 11:12 PM, John Arthorne wrote:

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:

05/19/2010 10:50 PM

Please respond to
Cross project issues

Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
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?</repo/uri>

so for example ... we'd have

for the common repo ... but could use

for webtools specific artifact repositories.

It would be the same amount of data coming back to, 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 ""?
> Was there a reason the instructions say "plugin"? For example, is
> there a trick to include a "tracking plugin" in a feature?

The "" 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.

cross-project-issues-dev mailing list

Back to the top