[
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:52 AM:
--------------------------------------------------------------
Example of using byteman:
According to present content of standalone.conf, it is needed to redefine JAVA_OPTS
environment's variable - you should include present content of this variable as well.
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
-jboss.modules.system.pkgs=org.jboss.byteman -Xms64m -Xmx512m -XX:MaxPermSize=256m
-Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true
-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
-Djava.awt.headless=true"
${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 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)
TS: Coverage reports
--------------------
Key: AS7-2022
URL:
https://issues.jboss.org/browse/AS7-2022
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Affects Versions: 7.1.0.Alpha1
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
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