Yes, that's the idea. Just put custom templates somewhere in your project
source tree, and things should work.
But there's indeed an inconsistency in the Modeler. Custom templates are still
modeled as absolute file paths in the Modeler preferences, and shared between
projects. This approach is
to summarize, currently templates to generate project classes must be realative
to project. Thanks Angus.
Atte. Juan Manuel Díaz Lara
On Monday, January 20, 2020, 10:09:34 AM CST, Andrus Adamchik
wrote:
> I recommend using a build task because you get consistency and you don't have
> I recommend using a build task because you get consistency and you don't have
> to re-select the templates over and over.
4.1 introduced storing cgen and dbimport preferences right in the DataMap XML
file, so picking templates every time should no longer be required. I suspect
the original
I can't directly answer your question as I don't use modeler directly for
class generation, but use a build task instead. I recommend using a build
task because you get consistency and you don't have to re-select the
templates over and over. I use *ant* for this, but it can be done with
maven too:
I am using Cayenn 4.1.RC and trying to user custom templates. I created a new
template, an selected in preferences, when generating I choose Advance and
selecte my new template, generations fails with "Unable to find resource ..."
and the template path, but this path does not have my home direct
