[ https://issues.jboss.org/browse/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka updated AS7-2022: ------------------------------ Description: There are some coverage jobs in Hudson: * Aggregated: https://hudson.qa.jboss.com/hudson//view/JBoss%20AS/job/jboss-as7-code-co... * Per module: https://hudson.qa.jboss.com/hudson/view/JBoss AS/job/JBoss-AS-7.0.x-unit-coverage/ We can also use Emma: http://emma.sourceforge.net/ Or this? http://www.eclemma.org/jacoco/index.html was: There are some coverage jobs in Hudson: * Aggregated: https://hudson.qa.jboss.com/hudson//view/JBoss%20AS/job/jboss-as7-code-co... * Per module: https://hudson.qa.jboss.com/hudson/view/JBoss AS/job/JBoss-AS-7.0.x-unit-coverage/ We can also use Emma: http://emma.sourceforge.net/ -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka updated AS7-2022: ------------------------------ Description: There are some coverage jobs in Hudson: * Aggregated: https://hudson.qa.jboss.com/hudson//view/JBoss%20AS/job/jboss-as7-code-co... * Per module: https://hudson.qa.jboss.com/hudson/view/JBoss AS/job/JBoss-AS-7.0.x-unit-coverage/ We can also use Emma: http://emma.sourceforge.net/ , http://mojo.codehaus.org/emma-maven-plugin/ Or this? http://www.eclemma.org/jacoco/index.html TCK coverage reports: http://www.qa.jboss.com/~smcgowan/CDI-TCK-Assertions/jsr299-tck-impl-cove... was: There are some coverage jobs in Hudson: * Aggregated: https://hudson.qa.jboss.com/hudson//view/JBoss%20AS/job/jboss-as7-code-co... * Per module: https://hudson.qa.jboss.com/hudson/view/JBoss AS/job/JBoss-AS-7.0.x-unit-coverage/ We can also use Emma: http://emma.sourceforge.net/ Or this? http://www.eclemma.org/jacoco/index.html TCK coverage reports: http://www.qa.jboss.com/~smcgowan/CDI-TCK-Assertions/jsr299-tck-impl-cove... -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda commented on AS7-2022: ---------------------------------------- We need to have coverage.xml file for Emma plugin on Hudson. Html report would be nice if I need it locally, by default xml report should be sufficient. -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-2022: ----------------------------------- Here's an example of using `jboss.modules.system.pkgs` with JProfiler: http://community.jboss.org/wiki/HackingOnAS7 -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Pavel Janousek edited comment on AS7-2022 at 12/5/11 8:07 AM: -------------------------------------------------------------- Example of using byteman: According to present content of standalone.conf, it is enough to define some content of JAVA_OPTS environment's variable (e.g. -javaagent with byteman) because in this case byteman is included by default (but JVM is started with different set of options!). This (for example) works for me: {code} export BYTEMAN_HOME=/home/pjanouse/tmp/byteman/byteman-1.6.0 export JAVA_OPTS="-javaagent:${BYTEMAN_HOME}/lib/byteman.jar=script:${EAP_HOME}/rules.txt,boot:${BYTEMAN_HOME}/lib/byteman.jar,sys:${BYTEMAN_HOME}/lib/byteman.jar,listener:false -Djboss.modules.system.pkgs=org.jboss.byteman" ${EAP_HOME}/bin/standalone.sh {code} For further inspection of present content of JAVA_OPTS see bin/standalone.conf Generally - it is enough to define jboss.modules.system.pkgs (-Djboss.modules.system.pkgs) with some package path - module is present in every ClassLoader path, also it seems as it isn't needed to create this package as regular AS7 module. (e.g. byteman isn't AS7 module by default) was (Author: pjanouse): Example of using byteman: According to present content of standalone.conf, it is enough to define some content of JAVA_OPTS environment's variable (e.g. -javaagent with byteman) because in this case byteman is included by default (but JVM is started with different set of option!). This (for example) works for me: {code} export BYTEMAN_HOME=/home/pjanouse/tmp/byteman/byteman-1.6.0 export JAVA_OPTS="-javaagent:${BYTEMAN_HOME}/lib/byteman.jar=script:${EAP_HOME}/rules.txt,boot:${BYTEMAN_HOME}/lib/byteman.jar,sys:${BYTEMAN_HOME}/lib/byteman.jar,listener:false -Djboss.modules.system.pkgs=org.jboss.byteman" ${EAP_HOME}/bin/standalone.sh {code} For further inspection of present content of JAVA_OPTS see bin/standalone.xml Generally - it is enough to define jboss.modules.system.pkgs (-Djboss.modules.system.pkgs) with some package path - module is present in every ClassLoader path, also it seems as it isn't needed to create this package as regular AS7 module. (e.g. byteman isn't AS7 module by default) -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda updated AS7-2022: ----------------------------------- Description: There are some coverage jobs in Hudson: * Aggregated: https://hudson.qa.jboss.com/hudson//view/JBoss%20AS/job/jboss-as7-code-co... * Per module: https://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-7.0.x-uni... We can also use Emma: http://emma.sourceforge.net/ , http://mojo.codehaus.org/emma-maven-plugin/ Or this? http://www.eclemma.org/jacoco/index.html TCK coverage reports: http://www.qa.jboss.com/~smcgowan/CDI-TCK-Assertions/jsr299-tck-impl-cove... was: There are some coverage jobs in Hudson: * Aggregated: https://hudson.qa.jboss.com/hudson//view/JBoss%20AS/job/jboss-as7-code-co... * Per module: https://hudson.qa.jboss.com/hudson/view/JBoss AS/job/JBoss-AS-7.0.x-unit-coverage/ We can also use Emma: http://emma.sourceforge.net/ , http://mojo.codehaus.org/emma-maven-plugin/ Or this? http://www.eclemma.org/jacoco/index.html TCK coverage reports: http://www.qa.jboss.com/~smcgowan/CDI-TCK-Assertions/jsr299-tck-impl-cove... -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-2022: ----------------------------------- Emma usage example in JBoss Tools: https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/ It's in the reports/emma-coverage nodule. http://anonsvn.jboss.org/repos/jbosstools/trunk/build/reports/emma-covera... -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda edited comment on AS7-2022 at 1/12/12 7:00 AM: ----------------------------------------------------------------- Current Cobertura based coverage jobs mentioned in description are for AS7 unit tests. Cobertura needs source codes to produce instrumented classes and jars. And it has problems when tests are in separate module and not in the same module as source codes. I was using Cobertura and Emma for code coverage on WS which has its testsuite in separate module and 2 submodules. I started with Cobertura and spent quite a lot of time to patch pom files. Than I had to merge Cobertura report files and it's not supported in maven plugin. I had to call ant from maven to merge these files and I had to know their exact location. Conclusion: Cobertura is good choice for code coverage for unit tests in modules but not good for testsuite module. I'm using Emmma for WS code coverage. It can instrument directly jars, source code are not necessary. My workflow is simple: instrument jars in AS, patch pom.xml for emma.rt.control.port, run tests and generate report. There are some problems (for example with emma.rt.control.port) but it's minor comparing problem with Cobertura. Conclusion: Works for my use use-case. Should work for your too. Examples: - https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbos... - https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbos... was (Author: rsvoboda): Current Cobertura based coverage jobs mentioned in description are for AS7 unit tests. Cobertura needs source codes to produce instrumented classes and jars. And it has problems when tests are in separate module and not in the same module as source codes. I was using Cobertura and Emma for code coverage on WS which has its testsuite in separate module and 2 submodules. I started with Cobertura and spent quite a lot of time to patch pom files. Than I had to merge Cobertura report files and it's not supported in maven plugin. I had to call ant from maven to merge these files and I had to know their exact location. Conclusion: Cobertura is good choice for code coverage for unit tests in modules but not good for testsuite module. I'm using Emmma for WS code coverage. It can instrument directly jars, source code are not necessary. My workflow is simple: instrument jars in AS, patch pom.xml for emma.rt.control.port, run tests and generate report. There are some problems (for example with emma.rt.control.port) but it's minor comparing problem with Cobertura. Conclusion: Works for my use use-case. Should work for your too. Examples: - https://hudson.qa.jboss.com/hudson/view/EAP6-jbossws/job/eap6-jbossws-emm... - https://hudson.qa.jboss.com/hudson/view/EAP6-jbossws/job/eap6-jbossws-emm... -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-2022: ----------------------------------- JaCoCo Maven plugin naively assumes that class files must be located in ${basedir}/target/classes. Need to resort to Ant task <jacoco:report> - see <classfiles>. {code:plain} [INFO] --- jacoco-maven-plugin:0.5.5.201112152213:report (ts.jacoco.report) @ jboss-as-testsuite-integration-smoke --- [ERROR] Error while creating report: basedir /home/ondra/work/AS7/ozizka-git/testsuite/integration/smoke/target/classes does not exist java.lang.IllegalStateException: basedir /home/ondra/work/AS7/ozizka-git/testsuite/integration/smoke/target/classes does not exist at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550) at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584) at org.jacoco.maven.ReportMojo.getFilesToAnalyze(ReportMojo.java:233) {code} -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka edited comment on AS7-2022 at 1/14/12 11:27 PM: ------------------------------------------------------------- JaCoCo Maven plugin naively assumes that class files must be located in ${basedir}/target/classes. Need to resort to Ant task <jacoco:report> - see <classfiles>. (Confirmed: https://sourceforge.net/projects/eclemma/forums/forum/614869/topic/479057... ) {code} [INFO] --- jacoco-maven-plugin:0.5.5.201112152213:report (ts.jacoco.report) @ jboss-as-testsuite-integration-smoke --- [ERROR] Error while creating report: basedir /home/ondra/work/AS7/ozizka-git/testsuite/integration/smoke/target/classes does not exist java.lang.IllegalStateException: basedir /home/ondra/work/AS7/ozizka-git/testsuite/integration/smoke/target/classes does not exist at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550) at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584) at org.jacoco.maven.ReportMojo.getFilesToAnalyze(ReportMojo.java:233) at org.jacoco.maven.ReportMojo.createBundle(ReportMojo.java:136) at org.jacoco.maven.ReportMojo.createReport(ReportMojo.java:115) at org.jacoco.maven.ReportMojo.executeMojo(ReportMojo.java:89) at org.jacoco.maven.AbstractJacocoMojo.execute(AbstractJacocoMojo.java:66) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) {code} was (Author: ozizka): JaCoCo Maven plugin naively assumes that class files must be located in ${basedir}/target/classes. Need to resort to Ant task <jacoco:report> - see <classfiles>. {code} [INFO] --- jacoco-maven-plugin:0.5.5.201112152213:report (ts.jacoco.report) @ jboss-as-testsuite-integration-smoke --- [ERROR] Error while creating report: basedir /home/ondra/work/AS7/ozizka-git/testsuite/integration/smoke/target/classes does not exist java.lang.IllegalStateException: basedir /home/ondra/work/AS7/ozizka-git/testsuite/integration/smoke/target/classes does not exist at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550) at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584) at org.jacoco.maven.ReportMojo.getFilesToAnalyze(ReportMojo.java:233) at org.jacoco.maven.ReportMojo.createBundle(ReportMojo.java:136) at org.jacoco.maven.ReportMojo.createReport(ReportMojo.java:115) at org.jacoco.maven.ReportMojo.executeMojo(ReportMojo.java:89) at org.jacoco.maven.AbstractJacocoMojo.execute(AbstractJacocoMojo.java:66) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) {code} -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka edited comment on AS7-2022 at 1/17/12 12:45 AM: ------------------------------------------------------------- JaCoCo Maven plugin naively assumes that class files must be located in ${basedir}/target/classes. Need to resort to Ant task <jacoco:report> - see <classfiles>. (Confirmed: https://sourceforge.net/projects/eclemma/forums/forum/614869/topic/479057... ) {code} [INFO] --- jacoco-maven-plugin:0.5.5.201112152213:report (ts.jacoco.report) @ jboss-as-testsuite-integration-smoke --- [ERROR] Error while creating report: basedir /home/ondra/work/AS7/ozizka-git/testsuite/integration/smoke/target/classes does not exist java.lang.IllegalStateException: basedir /home/ondra/work/AS7/ozizka-git/testsuite/integration/smoke/target/classes does not exist at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550) at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584) at org.jacoco.maven.ReportMojo.getFilesToAnalyze(ReportMojo.java:233) at org.jacoco.maven.ReportMojo.createBundle(ReportMojo.java:136) at org.jacoco.maven.ReportMojo.createReport(ReportMojo.java:115) at org.jacoco.maven.ReportMojo.executeMojo(ReportMojo.java:89) at org.jacoco.maven.AbstractJacocoMojo.execute(AbstractJacocoMojo.java:66) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) {code} JaCoCo RFE: https://sourceforge.net/tracker/?func=detail&aid=3474708&group_id... was (Author: ozizka): JaCoCo Maven plugin naively assumes that class files must be located in ${basedir}/target/classes. Need to resort to Ant task <jacoco:report> - see <classfiles>. (Confirmed: https://sourceforge.net/projects/eclemma/forums/forum/614869/topic/479057... ) {code} [INFO] --- jacoco-maven-plugin:0.5.5.201112152213:report (ts.jacoco.report) @ jboss-as-testsuite-integration-smoke --- [ERROR] Error while creating report: basedir /home/ondra/work/AS7/ozizka-git/testsuite/integration/smoke/target/classes does not exist java.lang.IllegalStateException: basedir /home/ondra/work/AS7/ozizka-git/testsuite/integration/smoke/target/classes does not exist at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550) at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584) at org.jacoco.maven.ReportMojo.getFilesToAnalyze(ReportMojo.java:233) at org.jacoco.maven.ReportMojo.createBundle(ReportMojo.java:136) at org.jacoco.maven.ReportMojo.createReport(ReportMojo.java:115) at org.jacoco.maven.ReportMojo.executeMojo(ReportMojo.java:89) at org.jacoco.maven.AbstractJacocoMojo.execute(AbstractJacocoMojo.java:66) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) {code} https://sourceforge.net/tracker/?func=detail&aid=3474708&group_id... -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka edited comment on AS7-2022 at 1/20/12 10:56 AM: ------------------------------------------------------------- Partial success - JaCoCo creates the .exec files, and the report task works. Yet to fix it's input. http://maven.40175.n5.nabble.com/Inline-Ant-tasks-not-working-Namespace-p... was (Author: ozizka): Partial success - JaCoCo creates the .exec files, and the report task works. Yet to fix it's input. -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-2022: ----------------------------------- ./build.sh clean install -DskipTests -Dcoverage ./integration-tests.sh clean install -DallTests -Dcoverage ./integration-tests.sh site -DallTests -Dcoverage ## Must run in separatedly. -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka edited comment on AS7-2022 at 1/24/12 3:10 PM: ------------------------------------------------------------ {code:bash} ./build.sh clean install -DskipTests -Dcoverage ./integration-tests.sh clean install -DallTests -Dcoverage ./integration-tests.sh site -DallTests -Dcoverage ## Must run in separatedly. #Alternatively: mvn site -rf testsuite -DallTests -Dcoverage {code} was (Author: ozizka): {code:bash} ./build.sh clean install -DskipTests -Dcoverage ./integration-tests.sh clean install -DallTests -Dcoverage ./integration-tests.sh site -DallTests -Dcoverage ## Must run in separatedly. {code} -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda commented on AS7-2022: ---------------------------------------- Where is that jub running? Are you using JaCoCo or Emma? -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka resolved AS7-2022. ------------------------------- Resolution: Done -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-2022: ----------------------------------- Documented in https://docs.jboss.org/author/display/AS71/AS+7+Integration+Testsuite+Use... -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-2022: ----------------------------------- Implemented. Notes: 1) Domain and compat are not yet included, I'm waiting for other good run. 2) Jenkins job is not stable enough, often it fails due to various bugs, e.g. AS7-3128 or NFS file locks etc. 3) Some jar files had to be excluded because of duplicated classes, see Until that is fixed (or JaCoCo supports that), those jars won't be included in JaCoCo report. 4) You can sort by columns by clicking on their headers. 5) Sources are included this time! Only for AS code though. Example: http://www.qa.jboss.com/~ozizka/AS7/coverage/2012-03-07/html/org.jboss.as... * Example report: ** Browse: http://www.qa.jboss.com/~ozizka/AS7/coverage/2012-03-07/html/ ** Download: http://www.qa.jboss.com/~ozizka/AS7/coverage/2012-03-07/coverage-report.zip * Jenkins job: https://hudson.qa.jboss.com/hudson/job/AS7-TS-valid-jacoco/ * Pull request: https://github.com/jbossas/jboss-as/pull/1733 -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka reopened AS7-2022: ------------------------------- -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka closed AS7-2022. ----------------------------- Resolution: Done Merged. Jenkins job: https://hudson.qa.jboss.com/hudson/view/ESSC/job/AS7-TS-valid-jacoco/ -- 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/AS7-2022?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-2022: ----------------------------------- Adding Jacoco as a global module: {code:xml} <subsystem xmlns="urn:jboss:domain:ee:1.0" > <global-modules> <module name="org.jacoco" slot="main" /> </global-modules> </subsystem> {code} -- 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