[ https://issues.jboss.org/browse/JBDS-1876?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-1876: ----------------------------- Description: {code} 2011-10-07 15:42:31) nickboldt: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job... is failing due to emma coverage for bpel (2011-10-07 15:42:57) nickboldt: it's failing to generate emma coverage because the sources for o.e.bpel.* aren't in the workspace, so the build is therefore red (2011-10-07 15:43:28) ldimaggi: ok? (2011-10-07 15:43:51) nickboldt: I'm wondering if you're ok w/ just disabling code coverage for bpel, or if you want us to figure out some way to fetch org.eclipse.bpel.* sources into the .tests job's workspace so that it can properly do the emma code coverage reporting (2011-10-07 15:44:32) ldimaggi: 1) For today disable emma (2011-10-07 15:44:41) ldimaggi: 2) On Monday - let's try to fix it {code} was: {code} 2011-10-07 15:42:31) nickboldt: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job... is failing due to emma coverage for bpel (2011-10-07 15:42:57) nickboldt: it's failing to generate emma coverage because the sources for o.e.bpel.* aren't in the workspace, so the build is therefore red (2011-10-07 15:43:28) ldimaggi: ok? (2011-10-07 15:43:51) nickboldt: I'm wondering if you're ok w/ just disabling code coverage for bpel, or if you want us to figure out some way to fetch org.eclipse.bpel.* sources into the .tests job's workspace so that it can properly do the emma code coverage reporting (2011-10-07 15:44:32) ldimaggi: 1) For today disable emma (2011-10-07 15:44:41) ldimaggi: 2) On Monday - let's try to fix it Solution is probably going to be something like scripting this: 1. fetch zip of upstream o.e.bpel update site from eclipse.org 2. unzip site, unzip source plugins into ${WORKSPACE}/sources/plugins/ -- 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

[ https://issues.jboss.org/browse/JBDS-1876?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-1876: -------------------------------- Fix Version/s: 5.0.0.Beta1 (was: 5.0.0.M4) not blocking -- 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

[ https://issues.jboss.org/browse/JBDS-1876?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-1876. --------------------------------- Resolution: Done eclemma gather coverage data only for loaded classes, which means final coverage statistic is usually higher that real coverage, because it dosen't consider classes that that wasn't loaded during test. To get real coverage for all classes metadata should be generated manually for plugins included in coverage report. Now it is not possible for plugins that are outside component codebase and are not part of the build. I fixed error by skipping metadata generation for unreachable plugins, but it means coverage report shows results higher then they really are. -- 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