Hi Kenney
On 9/4/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
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 f
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
help here... I recently moved to TestNG for a couple of
> projects and I will definitively try to make surefire support more
> robust.
>
> I committed a few long standing patches, but the commit for
> http://jira.codehaus.org/browse/SUREFIRE-53 it's probably not the
> culprit f
se,
first of all thanks for your patches for the surefire TestNG provider
and for your help here... I recently moved to TestNG for a couple of
projects and I will definitively try to make surefire support more
robust.
I committed a few long standing patches, but the commit for
http://jira.codehaus
://jira.codehaus.org/browse/SUREFIRE-53 it's probably not the
culprit for the problems you see (that patch just assure that the
original classloader gets reset after running surefire).
So that should depend on a previous change by Kenney:
http://svn.apache.org/viewvc/maven/surefire/trunk/surefire-b
On 03/09/2006, at 7:39 AM, Jesse Kuhnert wrote:
Sorry, I shouldn't be telling you guys what to do..
Yeah, you should be busy writing the tests :D
It is kind of ironic how few tests the testing framework has :(
- Brett
-
To
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) instea
