Hey

How far we want to go on with the ToolingAPI compatibility test suite?

At this moment we've got coverage for latest consumer vs 1.0-M3+
provider. Do we also want coverage for 1.0-M3+ consumer VS 1.0-M3+
provider? It's possible but tricky and potentially expensive. Some
challenges:
- the tests must have some fixed old version of ToolingAPI consumer on
the classpath. Ideally they should not have latest Gradle code on the
classpath.
- the tests cannot use our internal test harness code (or
alternatively we have to release the test harness code...)

Adam, gang, any thoughts?

Cheers!

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to