Thanks again for reporting this. Yes, there are quite a few generated objects that suffer from this problem. A fix has been committed for jOOQ 3.3 and will be merged to jOOQ 3.2.3
Cheers Lukas 2014/1/9 Lukas Eder <[email protected]> > When I wrote that line of code, I knew that my guilty conscience would > eventually punish me. Kind of like: > > [image: goto] > From http://xkcd.com/292/ > > OK, this should be fixed. Thanks for the hint: > https://github.com/jOOQ/jOOQ/issues/2937 > > > 2014/1/9 Darren S <[email protected]> > >> I know this is especially pedantic but if your schema objects don't have >> comments associated with them, the generated Java code will have trailing >> white space, which will be treated as a white space errors in git and other >> tools. For example the below code >> >> out.tab(1).javadoc("Setter for <code>%s</code>. %s", name, >> comment); >> >> So if you have a git commit hook that checks for white space errors, it >> will catch the jOOQ generated code. >> >> Darren >> >> -- >> You received this message because you are subscribed to the Google Groups >> "jOOQ User Group" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
