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

[Vlado Pakan (JIRA)]

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

Vlado Pakan commented on JBIDE-16214:
-------------------------------------

Jenkins plugin is not so important we can use also script to generate code coverage reports but for sure we need to have code coverage published to Sonar.

Results published to Sonar seams to be correct.

I think you should not waste your time to tweak your script regarding to multiple class issue. It has to be fixed in JBT and I don't think that you will find a way how to fix it in code coverage generation script. This is coming from code coverage analyze done by some class from jacocoant.jar so I guess it's not under developer control unless there is some property which allow you to ignore  this exception IMHO.
                
> 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