Update the way the bean templates are defined and code is generated

[daviddphillips]

** Allow classes to have any name (no Def) required
** Classes that are up for generation must be in a package called *..bbbtemplate
** All generated classes will generate classes with the same name to *.
** This allows the consumer of the library to add an exclusion for the *..bbbtemplate package if desired

[michapringle]

For example, If I want two classes in my ca.mpringle.bean package, I

• add the package ca.mpringle.bean.bbbtemplate,
• add the 2 definition files in that package,
• run the generation tool

then I would have this result (generated code in the generated dir of course)

.
├── bean
│   ├── Address.java
│   ├── bbbtemplate
│   │   ├── Address.java
│   │   └── Person.java
│   └── Person.java

[daviddphillips]

Ha... BeanBuilder has this feature (you requested it). You can put the Defs in a package called 'def' and it will genererate the beans in the package above! :) https://github.com/michapringle/codesorcerer/blob/master/spells/src/main/java/com/codesorcerer/generators/def/BeanDefInputBuilder.java (Line 94)

[michapringle]

Awesome. Those files can have any name then?

[daviddphillips]

Yes... the name of the class in the a.b.c.def package will be the name of the generaged class in the a.b.c package.

…

On Tue, May 29, 2018 at 9:33 AM Micha Pringle ***@***.***> wrote: Awesome. Those files can have any name then? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA2KnI7-bVxCXtMzZYvQR0tTLhcTSG45ks5t3XhHgaJpZM4UQp5X> .