Currently, it's a bit of a trick trying to get a javaagent in use with
your test cases. Here's the boiler plate pom text:
http://cwiki.apache.org/OPENEJBx30/javaagent-with-maven-surefire.html
It'd be really great if we could just do it like this:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<forkMode>pertest</forkMode>
<javaagent>
<groupId>org.apache.openejb</groupId>
<artifactId>openejb-javaagent</artifactId>
<version>3.0</version>
<options>the optional javaagent options string</options>
</javaagent>
</configuration>
</plugin>
The plugin could get the path to the artifact in the local repo and
prepend the string "-javaagent:<jarpath>[=<options>]" to the value of
argLine if there is one, similar to how the classpath is created.
Seems like we could just take part of the maven-dependency-plugin and
reuse it in the surefire plugin.
I've hacked on some plugins before, but the surefire one seems a
little more complicated than the typical plugin. Anyone with some
surefire expertise interested in working on this?
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
