[JGRP-1740] Fix byteman tests on Windows.

[rachmatowicz]

See this issue for details: https://issues.jboss.org/browse/JGRP-1740

[belaban]

This failed:
[linux]/home/bela/JGroups$ java -version
java version "1.6.0_43"
Java(TM) SE Runtime Environment (build 1.6.0_43-b01)
Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)
[linux]/home/bela/JGroups$ ant byteman
Buildfile: /home/bela/JGroups/build.xml

keyStoreGenerated:

check-jars-exist:

check-ivy-exists:

get-ivy:

define-ivy-task:

retrieve:

prepare:

compile:

makeKeystore:

postcompile:

define-testng-task:

byteman:
[testng] Error occurred during initialization of VM
[testng] agent library failed to init: instrument
[testng] Error opening zip file or JAR manifest missing : /home/bela/JGroups/lib/byteman.jar
[testng] The tests failed.

[belaban]

The correct JAR is byteman-2.1.3.jar, but I don't want to hard code this in build.xml...

[rachmatowicz]

Hmm, this reminds me of a discrepancy I found when testing on Windows. Before you moved to ivy, you used to include byteman.jar and byteman-version.jar in lib. Once you moved to ivy, the non-versioned jars are no longer present. I was going to add a step to ivy to recreate the aliasing, but know zero about ivy. Would that be a way around this issue?

[rachmatowicz]

I've added a small ant task instance to make a copy of byteman-version.jar to byteman.jar which should fix the problem.

WDYT?

[belaban]

I applied the removal of 'scripts' from the dir and adding it to the classpath. However, I don't want to apply the kludge to locate the byteman JAR just because this doesn't work on Windoze. We have to find a better way.