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

[Mickael Istria (JIRA)]

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

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