4:01 a.m.
Mickael Istria created JBDS-2017:
------------------------------------
Summary: Investigate usage of Jacoco report file as Usage collector
Key: JBDS-2017
URL: https://issues.jboss.org/browse/JBDS-2017
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Build, P2 Enabled Product, Usage Reporting
Reporter: Mickael Istria
Assignee: Nick Boldt
Using the jacoco java.agent is pretty simple to set up and generates a coverage report
file without affecting performances.
We could think about starting JBDS with this java.agent and consume the Jacoco report
files to get "technical" usage report.
Same could apply to JBoss tools by using p2 touchpoint to modify eclipse.ini when
installing an IU:
http://pweclipse.blogspot.com/2012/02/p2-can-update-your-eclipseini.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:22 a.m.
[
https://issues.jboss.org/browse/JBDS-2017?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2017:
-------------------------------------------
interesting idea but how would we collect the data ? How big are those datafiles ?
Could be a consideration as something for our usage plugin...
Investigate usage of Jacoco report file as Usage collector
----------------------------------------------------------
Key: JBDS-2017
URL: https://issues.jboss.org/browse/JBDS-2017
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Build, P2 Enabled Product, Usage Reporting
Reporter: Mickael Istria
Assignee: Nick Boldt
Using the jacoco java.agent is pretty simple to set up and generates a coverage report
file without affecting performances.
We could think about starting JBDS with this java.agent and consume the Jacoco report
files to get "technical" usage report.
Same could apply to JBoss tools by using p2 touchpoint to modify eclipse.ini when
installing an IU: http://pweclipse.blogspot.com/2012/02/p2-can-update-your-eclipseini.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:24 a.m.
[
https://issues.jboss.org/browse/JBDS-2017?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2017:
-------------------------------------------
one concern is how to generate these knowing jacoco is sensitive to the exact .class files
for reporting and how to use this to track/identify which overall features actually get
used vs very detailed info.
Investigate usage of Jacoco report file as Usage collector
----------------------------------------------------------
Key: JBDS-2017
URL: https://issues.jboss.org/browse/JBDS-2017
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Build, P2 Enabled Product, Usage Reporting
Reporter: Mickael Istria
Assignee: Nick Boldt
Using the jacoco java.agent is pretty simple to set up and generates a coverage report
file without affecting performances.
We could think about starting JBDS with this java.agent and consume the Jacoco report
files to get "technical" usage report.
Same could apply to JBoss tools by using p2 touchpoint to modify eclipse.ini when
installing an IU: http://pweclipse.blogspot.com/2012/02/p2-can-update-your-eclipseini.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:26 a.m.
[
https://issues.jboss.org/browse/JBDS-2017?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-2017:
--------------------------------------
interesting idea but how would we collect the data ?
We would need the user to upload them. We could think of a pop-up that opens from time to
time telling "Upload information about my usage of the software to JBoss
community".
How big are those datafiles ?
I think for a normal usage of an IDE and monitory org.jboss.tools.* class usage,
they'll be big! That's something we can already try I guess.
Investigate usage of Jacoco report file as Usage collector
----------------------------------------------------------
Key: JBDS-2017
URL: https://issues.jboss.org/browse/JBDS-2017
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Build, P2 Enabled Product, Usage Reporting
Reporter: Mickael Istria
Assignee: Nick Boldt
Using the jacoco java.agent is pretty simple to set up and generates a coverage report
file without affecting performances.
We could think about starting JBDS with this java.agent and consume the Jacoco report
files to get "technical" usage report.
Same could apply to JBoss tools by using p2 touchpoint to modify eclipse.ini when
installing an IU: http://pweclipse.blogspot.com/2012/02/p2-can-update-your-eclipseini.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:14 a.m.
[
https://issues.jboss.org/browse/JBDS-2017?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-2017:
--------------------------------------
To give it a try to an existing Eclipse installation with JBoss Tools in it:
* get latest Jacoco from here: http://www.eclemma.org/jacoco/
* extract lib/jacocoagent.jar into your eclipse/ folder (beside of the eclipse launcher)
* add a line to eclipse.ini, just after the "-vmargs" line:
-javaagent:jacocoagent.jar=destfile=usage.exec,append=true,includes=org.jboss.tools.*
(I think you have to put this stuff somewhere inside the .app for a Mac)
Then Eclipse will generate you a usage.exec file beside of the launcher, you can have a
look at it using EclEmma Eclipse plugin: http://www.eclemma.org/userdoc/importexport.html
Investigate usage of Jacoco report file as Usage collector
----------------------------------------------------------
Key: JBDS-2017
URL: https://issues.jboss.org/browse/JBDS-2017
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Build, P2 Enabled Product, Usage Reporting
Reporter: Mickael Istria
Assignee: Nick Boldt
Using the jacoco java.agent is pretty simple to set up and generates a coverage report
file without affecting performances.
We could think about starting JBDS with this java.agent and consume the Jacoco report
files to get "technical" usage report.
Same could apply to JBoss tools by using p2 touchpoint to modify eclipse.ini when
installing an IU: http://pweclipse.blogspot.com/2012/02/p2-can-update-your-eclipseini.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:03 a.m.
[
https://issues.jboss.org/browse/JBDS-2017?page=com.atlassian.jira.plugin....
]
Mickael Istria reassigned JBDS-2017:
------------------------------------
Assignee: Mickael Istria (was: Nick Boldt)
Investigate usage of Jacoco report file as Usage collector
----------------------------------------------------------
Key: JBDS-2017
URL: https://issues.jboss.org/browse/JBDS-2017
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Build, P2 Enabled Product, Usage Reporting
Reporter: Mickael Istria
Assignee: Mickael Istria
Using the jacoco java.agent is pretty simple to set up and generates a coverage report
file without affecting performances.
We could think about starting JBDS with this java.agent and consume the Jacoco report
files to get "technical" usage report.
Same could apply to JBoss tools by using p2 touchpoint to modify eclipse.ini when
installing an IU: http://pweclipse.blogspot.com/2012/02/p2-can-update-your-eclipseini.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:03 a.m.
[
https://issues.jboss.org/browse/JBDS-2017?page=com.atlassian.jira.plugin....
]
Mickael Istria updated JBDS-2017:
---------------------------------
Priority: Minor (was: Major)
Investigate usage of Jacoco report file as Usage collector
----------------------------------------------------------
Key: JBDS-2017
URL: https://issues.jboss.org/browse/JBDS-2017
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Build, P2 Enabled Product, Usage Reporting
Reporter: Mickael Istria
Assignee: Mickael Istria
Priority: Minor
Using the jacoco java.agent is pretty simple to set up and generates a coverage report
file without affecting performances.
We could think about starting JBDS with this java.agent and consume the Jacoco report
files to get "technical" usage report.
Same could apply to JBoss tools by using p2 touchpoint to modify eclipse.ini when
installing an IU: http://pweclipse.blogspot.com/2012/02/p2-can-update-your-eclipseini.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:13 a.m.
[
https://issues.jboss.org/browse/JBDS-2017?page=com.atlassian.jira.plugin....
]
Vlado Pakan updated JBDS-2017:
------------------------------
Attachment: usage.exec
Report from JBT 3.3.0.beta1a
Investigate usage of Jacoco report file as Usage collector
----------------------------------------------------------
Key: JBDS-2017
URL: https://issues.jboss.org/browse/JBDS-2017
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Build, P2 Enabled Product, Usage Reporting
Reporter: Mickael Istria
Assignee: Mickael Istria
Priority: Minor
Attachments: usage.exec
Using the jacoco java.agent is pretty simple to set up and generates a coverage report
file without affecting performances.
We could think about starting JBDS with this java.agent and consume the Jacoco report
files to get "technical" usage report.
Same could apply to JBoss tools by using p2 touchpoint to modify eclipse.ini when
installing an IU: http://pweclipse.blogspot.com/2012/02/p2-can-update-your-eclipseini.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:15 a.m.
[
https://issues.jboss.org/browse/JBDS-2017?page=com.atlassian.jira.plugin....
]
Vlado Pakan edited comment on JBDS-2017 at 2/24/12 3:14 AM:
------------------------------------------------------------
Report from JBT 3.3.0.beta1a attached
was (Author: vpakan):
Report from JBT 3.3.0.beta1a
Investigate usage of Jacoco report file as Usage collector
----------------------------------------------------------
Key: JBDS-2017
URL: https://issues.jboss.org/browse/JBDS-2017
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Build, P2 Enabled Product, Usage Reporting
Reporter: Mickael Istria
Assignee: Mickael Istria
Priority: Minor
Attachments: usage.exec
Using the jacoco java.agent is pretty simple to set up and generates a coverage report
file without affecting performances.
We could think about starting JBDS with this java.agent and consume the Jacoco report
files to get "technical" usage report.
Same could apply to JBoss tools by using p2 touchpoint to modify eclipse.ini when
installing an IU: http://pweclipse.blogspot.com/2012/02/p2-can-update-your-eclipseini.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:43 a.m.
[
https://issues.jboss.org/browse/JBDS-2017?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-2017:
--------------------------------------
Thanks Vlado,
Can you tell us what scenario was used to generate this report? How long was it, which
components you used?
We are trying to guess how big can be a jacoco.exec file for a "normal"
end-usage of JBoss Tools.
Investigate usage of Jacoco report file as Usage collector
----------------------------------------------------------
Key: JBDS-2017
URL: https://issues.jboss.org/browse/JBDS-2017
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Build, P2 Enabled Product, Usage Reporting
Reporter: Mickael Istria
Assignee: Mickael Istria
Priority: Minor
Attachments: usage.exec
Using the jacoco java.agent is pretty simple to set up and generates a coverage report
file without affecting performances.
We could think about starting JBDS with this java.agent and consume the Jacoco report
files to get "technical" usage report.
Same could apply to JBoss tools by using p2 touchpoint to modify eclipse.ini when
installing an IU: http://pweclipse.blogspot.com/2012/02/p2-can-update-your-eclipseini.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:48 a.m.
[
https://issues.jboss.org/browse/JBDS-2017?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2017:
-------------------------------------------
not a big priority but I like the idea.
Would be interesting to at least have a plugin that wuold allow enabling/disabling jacoco
and easily send/attach the usage back to us.
Investigate usage of Jacoco report file as Usage collector
----------------------------------------------------------
Key: JBDS-2017
URL: https://issues.jboss.org/browse/JBDS-2017
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Build, P2 Enabled Product, Usage Reporting
Reporter: Mickael Istria
Assignee: Mickael Istria
Priority: Minor
Fix For: 5.x
Attachments: usage.exec
Using the jacoco java.agent is pretty simple to set up and generates a coverage report
file without affecting performances.
We could think about starting JBDS with this java.agent and consume the Jacoco report
files to get "technical" usage report.
Same could apply to JBoss tools by using p2 touchpoint to modify eclipse.ini when
installing an IU: http://pweclipse.blogspot.com/2012/02/p2-can-update-your-eclipseini.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:48 a.m.
[
https://issues.jboss.org/browse/JBDS-2017?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen updated JBDS-2017:
--------------------------------------
Fix Version/s: 5.x
Investigate usage of Jacoco report file as Usage collector
----------------------------------------------------------
Key: JBDS-2017
URL: https://issues.jboss.org/browse/JBDS-2017
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Build, P2 Enabled Product, Usage Reporting
Reporter: Mickael Istria
Assignee: Mickael Istria
Priority: Minor
Fix For: 5.x
Attachments: usage.exec
Using the jacoco java.agent is pretty simple to set up and generates a coverage report
file without affecting performances.
We could think about starting JBDS with this java.agent and consume the Jacoco report
files to get "technical" usage report.
Same could apply to JBoss tools by using p2 touchpoint to modify eclipse.ini when
installing an IU: http://pweclipse.blogspot.com/2012/02/p2-can-update-your-eclipseini.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5114
days inactive
5179
days old
jbosstools-issues@lists.jboss.org
11 comments
3 participants
participants (3)
-
Max Rydahl Andersen (JIRA) -
Mickael Istria (JIRA)
-
Vlado Pakan (JIRA)