We don't have a very good story for testing the java generator. Currently we check in generated code into the trunk, and manually update it periodically, after the generator is updated. Part of the reason for this is that, given the existing project structure, attempting to use the sdo-plugin to dynamically generate classes while building the sdo-tools project causes maven to fail with a circular dependency, since the plugin project depends on the tools project for its function, and the tools project would be depending on the plugin project for its test function.
I don't know if its possible to test a plugin from within its own pom, or whether that's good or bad practise. It seems likely to be at least confusing, and probably prone to issues, such as bootstrapping a new version of the plugin failing. We could add another project to the SDO development set of projects, primarily for this kind of testing. Alternatively it is practically possible to add java generator tests to the tuscany specific project of the CTS, but this seems as though it might be inappropriate. Does anybody have any experience of best practices of testing a maven plugin, or any other suggestions? In the absence of any alternative proposals I will investigate adding an extra project to the Tuscany SDO development code. Regards, Kelvin.
