There is currently no support for a per module testsuite module. I
still have not settled all of the issues that revolve around this.
The reason you are getting these errors is because the build.xml files
are not meant to be nested such as you are doing. Early on this was
allowed (when plugins/ was around), but it was removed to simplify things.
Your best bet, short term would be to add the tests to JBoss/Testsuite,
add a special target to execute them.
Eventually we will have per module testsuites, and leave JBoss/Testsuite
for integration testing only, but it will take some time to get that to
work.
--jason
Francisco Reverbel wrote:
>On Thu, 7 Mar 2002, Jason Dillon wrote:
>
>>${project.thirdparty}
>>
>>--jason
>>
>
>This is what I get:
>
>/home/reverbel/jboss-all/iiop/testsuite/build.xml:62:
>/home/reverbel/jboss-all/iiop/thirdparty/sun/jaxp/lib not found.
>
>I want it to look for the libs in jboss-all/thirdparty, not in
>jboss-all/iiop/thirdparty. Tried
>
> <property name="project.thirdparty"
> value="${project.root}/../thirdparty"/>
>
>but it does not work.
>
>Is is strange that the error message refers to line 62, which is
>
> <property name="module.name" value="iiop-testsuite"/>
>
>I do not understand what this line has to do with the error.
>
>Best,
>
>Francisco
>
>
>
>
>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development