It will work, for sure. The main issue ist the lack of support for generics, which causes bad workarounds and conversions in different parts of the code. And I would like to update the commons configuration version, which is using generics.
Regards Martin Am 12. Februar 2019 01:50:41 MEZ schrieb Chris Graham <[email protected]>: >If it works... > >Is it really causing any issues at the moment? Or is this a nice to >have? > >Modello is also used by maven plugins. > >Sent from my iPhone > >> On 12 Feb 2019, at 7:33 am, Martin <[email protected]> wrote: >> >> Hi, >> >> I would like to get rid of the code generation, mainly for >archiva-configuration, but maybe for the persistence domain classes >also. >> Why: >> - The code generation is using modello, which hasn't seen any new >releases in the last years. >> - Modello is not able to generate proper code with generics >> - It cannot be extended easily to add generics features >> - There is Java code in the modello xml file, which cannot be >recognized by any IDE ( program code in XML is really awkward ;- ) >> - The generated code is not part of the history and is only available >after some extra generation step (bad for IDEs) >> >> The code generation may reduce the work for writing boilerplate code, >but I don't think there is much change in these generated >> classes that justifies to keep it. >> >> So, if you have any concerns, please raise your hands. >> >> If not, I will add the currently generated code to the source tree >and git repository and deactivate the modello plugins in the maven >poms. >> >> Maybe we can find a better code generation solution in the future, >but for the time being the less time consuming solution would be to >deactivate >> code generation completely (in my opinion). >> >> Regards >> >> Martin >> >> >> -- This message was sent from mobile phone.
