[
https://issues.apache.org/jira/browse/SUREFIRE-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-179.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Add support for specifying and configuring java instrumentation agents for
> tests being launched in a new jvm
> ------------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-179
> URL: https://issues.apache.org/jira/browse/SUREFIRE-179
> Project: Maven Surefire
> Issue Type: New Feature
> Components: process forking
> Affects Versions: 2.0 (2.2 plugin)
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
