You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/01/21 23:24:21 UTC
[jira] Moved: (SUREFIRE-179) Add support for specifying and
configuring java instrumentation agents for tests being launched in a new
jvm
[ http://jira.codehaus.org/browse/SUREFIRE-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MSUREFIRE-171 to SUREFIRE-179:
-------------------------------------------------
Affects Version/s: (was: 2.0 (2.2 plugin))
Key: SUREFIRE-179 (was: MSUREFIRE-171)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> Add support for specifying and configuring java instrumentation agents for tests being launched in a new jvm
> ------------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-179
> URL: http://jira.codehaus.org/browse/SUREFIRE-179
> Project: Maven Surefire
> Issue Type: New Feature
> Reporter: Walco van Loon
> Attachments: javaagent-support.patch
>
>
> JDK 1.5 added a new feature for instrumenting byte code in Java (See java.lang.Instrument for more information). The attached patch adds support for configuration of java agents and agent dependencies on the surefire command line, when forking is enabled. The code used to configure the jvm argLine does not use any JDK 1.5 features. Test cases are included.
> The java.lang.Instrument approach has a few advantages:
> 1) no stale instrumented classes
> 2) no need for forked lifecycles and hacks to get the instrumented classes on the classpath
> 3) any class that is loaded into the jvm can be instrumented
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira