Better DTO Generation about che

[TylerJewell]

@skabashnyuk - was this discussed in the roadmap meeting?

[slemeur]

Yes it was and it is taken in the current sprint: IDEX-4273

[tareksha]

Hi @slemeur , can you please share more information about item IDEX-4273? is it connected to my contribution?

[TylerJewell]

@slemeur @skabashnyuk - I see that there are two open items for better DTO generation that are open on Codenvy's systems and nothing included in GitHub. What is the status of this improvement? @tareqhs - were your pull requests accepted?

[tareksha]

hi @TylerJewell , I did not open a pull request due to lack of technical feedback. The change itself is still there and open for discussions and pull request evaluation.

[TylerJewell]

@skabashnyuk - please have someone review & comment in the next sprint.

[TylerJewell]

@tareqhs @skabashnyuk - this issue is now officially the oldest one for Che! What is our plan here?

[skabashnyuk]

We made our analysis and concluded that:

The basic idea of the @tareqhs request pretty nice. Use annotation processor and string templates instead of current realization carries several positive moments makes the process of generating a more scalable, more obvious(due templates), easier to support(do not need custom Maven plugins). However, since the proposed implementation is not completed (no client-side templates) to the end and it is outdated. Also we need to bring the general idea and make our own implementation this issue.

List of issues

• Rework dto generator with string templates #2242
• Get rid of custom maven plugin in dto generator #2243

[TylerJewell]

@skabashnyuk - is this still in your backlog? Wondering what the prioirty of this should be relative to your other backlog items. Will you offer a suggestion?

[skabashnyuk]

we have this pr in our current sprint backlog.

[TylerJewell]

Crosslinked - is this the one:
#3103

[skabashnyuk]

Sorry I was wrong. We are working on #3103