[
https://issues.jboss.org/browse/JBDS-4014?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-4014:
----------------------------------
If we want to be able to use p2statusURL to track INSTALL, we'll need to customize the
metadata in the update site used to produce the devstudio rpm. I can work on a patch to
try to make that work if this is something we want to do. Can't recall the last time I
looked at the p2stats data -- it basically just pings
devstudio.redhat.com and produces a
404 in the apache log, which we can then scrape for install numbers. But if we're
hosting the rpm itself on
devstudio.redhat.com, we could also just look at the number of
downloads and assume anyone downloading the rpm has also installed it.
Track rh-eclipse46-devstudio-*.rpm version usage
------------------------------------------------
Key: JBDS-4014
URL:
https://issues.jboss.org/browse/JBDS-4014
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Feature Request
Components: usage
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Priority: Critical
Fix For: 10.2.0.AM1
We need to distinguish the following use cases:
1) Devstudio installed via RPM
2) Devstudio installed via P2 but on top of the "base" eclipse rpm
3) Devstudio installed traditionally (jar installer or p2)
As a bonus we could want to track if the DTS + devstudio rpms were both installed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)