Can you give some more details?
There are 2 classloaders created - one for surefire itself, containing
surefire code and the testing framework; the second one contains only
the test dependencies from the POM.
If your annotations can't be found, they're missing from the project test
path. Or the two classloaders described above aren't linked.
If it worked before, it shouldn't have, because the root classloader shouldn't
contain the testng annotations.
Could you provide a unit test?
-- Kenney
Jesse Kuhnert wrote:
Applying the patch mentioned has made running annotation based testng tests
b0rken. Ie before it was loading classes using a context of system class
loader. I've fixed this locally by calling createClassLoader(classpathurls,
childdelegation, true) (which uses system class loader by default) instead
of createClassLoader(classpathurls, null, childdelegation, true).
The recent application of old patches is definitely appreciated, but things
like this make me nervous for the future. There ~has~ to be a reasonable
way
to run unit tests against surefire that assert things aren't broken...The
logic of classloader dependencies is too fragile to not have tests...
Sorry, I shouldn't be telling you guys what to do..
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
