I wondered about that, but the functional tests module seems to be more
"support for functional tests" than functional tests itself. That means
that almost every test depends on mule-tests-functional and again I think
we get a loop (VM tests depend on mule-tests-functional which would depend
on VM).
I think they should go in something like a "functional tests" module
(which is what Andrew suggested too, I think), but the current
mule-tests-functional doesn't seem to be it (and should perhaps be renamed
to mule-module-functional-tests or similar?)
Does that make sense?
Andrew
> They could go into the functional-tests module
>
> Cheers,
>
> Ross Mason
>
> On 2 Oct 2007, at 19:40, andrew cooke wrote:
>
>>
>> Almost all the tests for the XML module are in the VM package to avoid
>> dependency loops in Maven (VM is used as the transport to test filters
>> that operate on XML payloads, etc; the VM tests depend on
>> mule-tests-functional which depends on mule-module-xml, so making XML
>> tests depend on VM would add a loop).
>>
>> One way to avoid this is to put the tests in mule-tests-
>> integration, but I
>> am reluctant to do that given that those do not run in CI.
>>
>> Any other suggestions/ideas on how better to arrange this?
>>
>> Thanks,
>> Andrew
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>
http://xircles.codehaus.org/manage_email>>
>
>
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
