[JIRA] [jacoco-plugin] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title Raj Bhaskar commented on JENKINS-15570 Re: Coverage report includes classes that have been excluded from Jacoco analysis I think I'm having the same issue. I package the Oracle JDBC driver as a local jar in my application (as it's not on maven) but it looks like although I'm excluding it in my pom, the plugin is still including it when doing its analysis. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title C. S. updated an issue Jenkins / JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Change By: C. S. Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title C. S. commented on JENKINS-15570 Re: Coverage report includes classes that have been excluded from Jacoco analysis We ran into the same issue. It is important for us to get it working, because we have a lot of generated classes, which should be excluded and it would be a mess to set up each Jenkins job according the new classes. So we decided to exclude the classes from the report via pom. But it seems that the jacoco plugin does its own match from classes to exec file. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Akos Kozak commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Still not working with plugin version 1.0.16 and Jenkins 1.563. Should we update? Or need to be fixed in the plugin! Thank you! 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Akos Kozak edited a comment on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Still not working 100%-ly with plugin version 1.0.16 and Jenkins 1.563. I made a smaller maven project where I got api and be modules. I set: pom.xml execution idcheck-coverage/id goals goalcheck/goal /goals configuration rules rule elementBUNDLE/element excludes exclude*api*/exclude /excludes limits limit counterLINE/counter valueCOVEREDRATIO/value minimum0.25/minimum /limit /limits /rule /rules /configuration /execution And the plugin works well. No api is wisible in the coverage. But if I do the same on our large project, if from one module Test a call will be done on an api, and therefor in the be classes this will be visible. However I would like to exclude api. Module A A-api: Interface to A service A-be : Service A implementation Module B B-api: Interface to B service B-be: Service B implementation From Service B implementation we call a method over A-api Interface to A service implementation. Therefore, the B-api will be excluded, but the A-api not! This is a bit disturbing, because the A-api should be also excluded. I hope I have right, and it is understandable what I wrote! 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Akos Kozak edited a comment on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Still not working 100%-ly with plugin version 1.0.16 and Jenkins 1.563. I made a smaller maven project where I got api and be modules. I set: pom.xml execution idcheck-coverage/id goals goalcheck/goal /goals configuration rules rule elementBUNDLE/element excludes exclude*api*/exclude /excludes limits limit counterLINE/counter valueCOVEREDRATIO/value minimum0.25/minimum /limit /limits /rule /rules /configuration /execution And the plugin works well. No api is visible in the coverage. But if I do the same on our large project, if from one module Test a call will be done on an api, and therefor in the be classes this will be visible. However I would like to exclude api. Module A A-api: Interface to A service A-be : Service A implementation Module B B-api: Interface to B service B-be: Service B implementation From Service B implementation we call a method over A-api Interface to A service implementation. Therefore, the B-api will be excluded, but the A-api not! This is a bit disturbing, because the A-api should be also excluded. I hope I have right, and it is understandable what I wrote! 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
