Hi, I already anticipated that response : ) And agree that ist bad practice : )
But I agree with your approach.. we first try it in our branch and if ist fine, we should start the release train and go for it : ) Julian Am 16.07.19, 10:16 schrieb "Christofer Dutz" <[email protected]>: Hi Julian, A big -1 for checking in generated code. We should simply release the build tools asap. I think it's in good shape and wanted to verify by testing it with more specs. So I would like you guys to test if the current solution suits your needs. So how about you trying to create the mspec and if this works and no changes on the plugin are needed, to release the build tools directly after my holidays? Chris Holen Sie sichOutlook für Android<https://aka.ms/ghei36> ________________________________ From: Julian Feinauer <[email protected]> Sent: Tuesday, July 16, 2019 9:18:09 AM To: [email protected] Cc: Volker Emmert Subject: Generated Drivers / DF1 Hi all, I had a short discussion with Chris and Volker (a new colleague of us) yesterday which is important for the list, I guess. First, I learned (sorry that I didn’t notice Chris!) that the generation of POJOs and serializers / deserializers in Java is totally finished. So if we agree on accepting this as first major step towards driver generation this is reached. BIG PROPS to Chris for making that happen! As we need another driver (DF1 protocol) I think the way will be the following for us: * Write an mspec file * Generate java pojos / factories * Write protocol logic in java on top of the pojos I suggest to also commit the generated files in the first run (until the maven plugin is released). @cdutz: we try to follow your docs as closely as possible but if further things are unclear we try to bring it back to you / the list / the docu. Julian
