[
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