🎉 Add Java destination generator

[tuliren]

What

• Add the code generator for java destination.
• This generator also takes care of UUID generation.

Pre-merge Checklist

• Merge after 🎉 New destination: S3 #3672 is merged. That PR has an interface change, and the template assumes that change has been merged to production.

Recommended reading order

1. plopfile.js
2. connector-templates/destination-java/README.md.hbs

[michel-tricot]

Can the template pass tests? I wonder if we should make the template an Echo to stdout with all the FIXMES

[michel-tricot]

Very nice :D

[tuliren]

Can the template pass tests? I wonder if we should make the template an Echo to stdout with all the FIXMES

What do you mean by "pass tests"? The newly generated connector code will pass the build task. Does that count?

Also not sure about the benefits of the echo approach. With that approach, no concrete file will be generated, right?

[michel-tricot]

build counts!

I am just thinking about AirbyteMessageConsumer is there something we can do to make it a bit easier to create or more guided?

[tuliren]

Got it. To clarify that the template files themselves are not part of any build task. It is the generated code from these templates that can pass the build.

The template is not much helpful in terms of facilitating the development of AirbyteMessageConsumer. That probably needs a CDK.