[jbosstools-issues] [JBoss JIRA] (JBIDE-16214) Code Coverage jobs needs to have locally available measured plugins

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-16214:
----------------------------------------

{quote}I think it's not problem of Sonar. jacoco.exec file is generated without links to class/jar files because they are installed from update site not from local file system.{quote}
Actually, the jacoco.exec file doesn't contain "linked" to filesystem. It contains the "ID" of classes is uses, and the issue is that it runs against pack200'd classes (from repo) and tries to report against non-pack200'd classes (from Maven build). The ID of the class is modified by pack200 so Jacoco reports can't understand the relationship between a pack200'd class and an plain one.

{quote}ame classpath as maven build{quote}
What's more interesting is the classpath of surefire tests. You can find it in <test>/target/work/configuration/config.ini, it's the osgi.bundles property. It's 100% sure that Sonar does NOT read it. I don't really know where it looks for class instead. I'd bet in the target/ folder of other modules.
                
> Code Coverage jobs needs to have locally available measured plugins
> -------------------------------------------------------------------
>
>                 Key: JBIDE-16214
>                 URL: https://issues.jboss.org/browse/JBIDE-16214
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: build
>    Affects Versions: 4.1.1.CR1
>            Reporter: Vlado Pakan
>            Assignee: Mickael Istria
>             Fix For: 4.1.x
>
>
> Code Coverage calculating via maven build returns 0% coverage because it's using source code and binary plugins installed from update site.
> When these are built locally prior to build calculating code coverage it returns correct results.
> Unfortunately sometimes maven build used plugins installed from update site instead of those which are locally build.
> We need to find way how to fix this.
> It's already reported here https://bugs.eclipse.org/bugs/show_bug.cgi?id=352560

--
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