Andrus Adamchik <andru..bjectstyle.org> wrote:
> Another idea - not sure how easy it is to factor out VPP stuff into a
> subclass. But if we can do that, we can have two tasks imported with
> Antlib, named something like cgen and cgen2.
>
> But then, if it is too much trouble, I guess making vpp Jar a
> requirement for code generation is not the end of the world. License
> permits us to distribute it with Cayenne (and we can actually trim the
> size of the Jar as cayenne.jar already includes Velocity).
Yeah, we can easily make a subclass of tool.CayenneGenerator and throw this
change on it.
However, we'd then be breaking "forward compatiblity" since everyone would
start embedding cgen2 in their builds, and we'd never be able to easily
deprecate cgen, or even make the default 1.2.
However, I am ok with either approach.
-Mike
This archive was generated by hypermail 2.0.0 : Mon May 23 2005 - 21:22:48 EDT