On 05/01/15 17:09, Alan Bateman wrote:
>
> Thanks for the update. So I'm curious how this worked previously, was
> this Maven plugin using its own class loader to load types from tools.jar?
Well, . . . maven was using its own classloader to load types from
/whatever jars/ it found in the classpath.
So, to test an app with BMUnit you need to add both the byteman jars
/and/ the tools jar to the classpath. e.g. from maven with Linux/Windows
(but not Mac OSX) the latter requirement means you add this dependency:
<dependency>
<groupId>com.sun</groupId>
<artifactId>tools</artifactId>
<version>1.6</version>
<scope>system</scope>
<systemPath>${tools.jar}</systemPath>
</dependency>
Of course, that fails if you are using JDK9. So, one of the changes
needed to build byteman-bmunit.jar with JDK9 is to add the dependency in
a profile conditional on the JDK version being in the range 1.6-1.8.
regards,
Andrew Dinn
-----------
Senior Principal Software Engineer
Red Hat UK Ltd
Registered in UK and Wales under Company Registration No. 3798903
Directors: Michael Cunningham (USA), Matt Parson (USA), Charlie Peters
(USA), Michael O'Neill (Ireland)
