[jbosstools-issues] [JBoss JIRA] (JBDS-2017) Investigate usage of Jacoco report file as Usage collector

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669470#comment-12669470 ] 

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