That's awesome Lukas, thank you! :-) Am Mittwoch, 3. April 2013 21:30:07 UTC+2 schrieb Lukas Eder: > > Hello > > #2366 is implemented for jOOQ 3.0: > https://github.com/jOOQ/jOOQ/issues/2366 > > It includes Peter's contribution and my own example addition, taking > prefix and suffix arguments for most GeneratorStrategy methods as JVM > parameters. These implementations are to be understood as working > examples, and as such, might be modified / adapted in the future. So, > use them at your own risk. > > For details, see: > > https://github.com/jOOQ/jOOQ/blob/master/jOOQ-codegen/src/main/java/org/jooq/util/example/JPrefixGeneratorStrategy.java > > > https://github.com/jOOQ/jOOQ/blob/master/jOOQ-codegen/src/main/java/org/jooq/util/example/JVMArgsGeneratorStrategy.java > > > Cheers > Lukas > > 2013/4/3 Lukas Eder <[email protected] <javascript:>>: > > As a general note: bashing Maven, Hibernate, etc. is off-topic for > > this list. Getting personal and emotional even more. If in doubt, > > please consider reading these rules: > > http://www.apache.org/dev/contrib-email-tips.html > > > > Apart from that, the appropriate place for rants is reddit ;-) > > > > This is my definite stand on this discussion: > > > > 1. Not all jOOQ users use Maven. > > 2. Maven has its place just like Hibernate. Those tools deserve more > respect. > > 3. I don't have time to implement #1171 > > (https://github.com/jOOQ/jOOQ/issues/1171) right now, but users had > > been requesting it for a long time > > 4. Libraries should ease the pain of their users. GeneratorStrategy > > had been causing pain to many users before, both Maven and non-Maven > > 5. jOOQ-codegen isn't really jOOQ's core. Some have looked at its the > > code generating code before and considered the whole module ... > > "bloat" ;-) So the jOOQ-codegen module will survive my adding this > > particular strategy class. > > 6. Peter's suggestion is a low-hanging fruit. I will add it as of > > #2366 (https://github.com/jOOQ/jOOQ/issues/2366). I will add it to an > > org.jooq.util.example package, which will be shipped with > > jOOQ-codegen. It is to be understood as a working example. > > > > Joachim, let's have a look at this paragraph: > > > >> "Oh dear I'll have to learn ALL THAT, that's going to be > >> another Hibernate experience where I can't know what I'm > >> actually doing, Jooq promised to be easy and in 1:1 > >> correspondence with SQL but it's not picking up new > >> features at an alarming rate, where is this whole thing > >> headed??" > > > > What exactly do you mean by "all that"? Feel free to create a new > > thread on this list, discussing concrete things that you feel should > > not be implemented in jOOQ. I am always open to suggestions and I have > > removed a lot of "bloat" already in jOOQ 3.0. Some examples can be > > seen here: > > > > All incompatible changes between 2.x and 3.0-RC1: > > > https://github.com/jOOQ/jOOQ/issues?labels=T%3A+incompatible+change%2CR%3A+fixed&milestone=17&page=1&state=closed > > > > > Removal of deprecated code > > https://github.com/jOOQ/jOOQ/issues/1887 > > > > Note that optimistic locking is already a deprecation candidate for 4.0 > > > > Cheers > > Lukas > > > > 2013/4/3 Peter Ertl <[email protected] <javascript:>>: > >> Hi Joachim, > >> > >> I think we both clearly showed our attitude. So here my final words > (before > >> things start getting emotional): > >> > >> I don't think we will bloat jOOQ by adding a very small class having a > >> one-line payload and being very simple. Neglecting it just because it's > >> bloat sounds a little too academic for me. > >> > >> The addition of the class will immediate solve a real-world problem for > >> people working with maven (which are quite many) and JPA / hibernate / > >> eclipselink / etc. (which are many as well). > >> > >> Just saying "you use maven / jpa / hibernate instead of [INSERT PRODUCT > >> HERE] so it's your own fault... you gotta do some really ugly work just > to > >> integrate jooq nicely" is not the best way to adapt new users. > >> > >> The current naming strategy integration *imho* is not adequate for > >> maven-only projects. > >> > >> Rolling a better naming strategy which integrates nicer into maven > should be > >> the final solution. However this is no easy task. Once we get there > nuking > >> the silly one-liner should not be a great deal. > >> > >> So yes, I would like to add some temporary "bloat". And "yes" it will > solve > >> some issues immediately. > >> > >> Cheers > >> Peter > >> > >> -- > >> 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] <javascript:>. > >> 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.
