[jbosstools-issues] [JBoss JIRA] (JBDS-2017) Investigate usage of Jacoco report file as Usage collector
Mickael Istria (JIRA)
jira-events at lists.jboss.org
Tue Feb 12 05:01:56 EST 2013
[ https://issues.jboss.org/browse/JBDS-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753617#comment-12753617 ]
Mickael Istria commented on JBDS-2017:
--------------------------------------
An blog I wrote about a year ago: http://mickaelistria.wordpress.com/2012/03/13/the-ultimate-usage-report-in-your-java-application-a-jacoco-exec-file/
Having a plugin to enable/disable Jacoco that wouldn't be easy since:
* We cannot enable agent programmatically
* this require to restart the JVM to enable agent
It would require to tweak the config.ini.
> 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: LATER
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list