[
https://issues.apache.org/jira/browse/TUSCANY-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462006
]
Kelvin Goodson commented on TUSCANY-1018:
-----------------------------------------
This raises the question of whether we always want to be testing against the
current generator pattern or whether some compatibility testing ought to be in
place. Having this old generated code in place does exercise some different
code paths in SDOUtil. This was in my mind when leaving this generated code in
the old pattern. I did have plans (and a sandbox version) to reorganize the
packaging of the test code to reflect a new compatibility category, but that
felt too much to do under TUSCANY-684. Perhaps we should have a mailing list
discussion on generated code compatibility testing before overwriting the old
generated code. This issue was on my mind when adding the pattern_version
identifier to the generated code.
> Unused data files for testing should be removed
> -----------------------------------------------
>
> Key: TUSCANY-1018
> URL: https://issues.apache.org/jira/browse/TUSCANY-1018
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-M3
> Reporter: Fuhwei Lwo
> Priority: Minor
> Fix For: Java-M3
>
>
> Statically generated Java files for testing under
> java/sdo/impl/src/test/java/com/example/simple were codegened by using the
> old code generator and no longer used by any test cases. They should be
> removed to avoid confusion.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
