Jon Elson-Green wrote:Indeed, in fact it's some classloader strangeness which I don't quite grok.
Now that I've had a test case fail, how can I achieve jar:install when I can't achieve test:test because Merlin is only looking at jars in the repository, (chicken and the egg paradox)? Is there a way to get it to use target/classes?
The test is already using target/classes. If you add a merlin.properties file to the working directory and add
I'm unable to load a dynamic class from a jar that's in the block inside the
testcase though I am able to load the same class outside of junit.
Fortunately I don't really need to understand it, that classes testcase really
belongs elsewhere, though this will complicate end to end tests.
Jon
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
