> > (I cannot split into more jars, long story...)`
Can you explain why you cannot create more than one project in your development environment? I'm interested in that "long story". 2017-12-21 13:14 GMT+01:00 Denis Miorandi <[email protected]>: > Ok. So whats informations more do you Need from me? > > Il 21 dic 2017 11:47 AM, "Lukas Eder" <[email protected]> ha scritto: > >> Before we prioritise, I'd like to really really understand why you have >> this limitation :) >> >> 2017-12-21 11:44 GMT+01:00 Denis Miorandi <[email protected]>: >> >>> tks Lukas for issue, my limitation it's at development time. >>> About priority. Probably there are a lot of people that work in hybrid >>> jpa+jooq scenario, I suppose, but I don't know. This is at you. To me this >>> feature have a great value, cause >>> I'm going to develop a lot of projects using great jhipster code >>> generator (spring-jpa+angular). >>> >>> Thanks >>> Denis >>> >>> >>> >>> Il giorno giovedì 21 dicembre 2017 11:28:15 UTC+1, Lukas Eder ha scritto: >>>> >>>> Hi Denis, >>>> >>>> 2017-12-21 11:12 GMT+01:00 Denis Miorandi <[email protected]>: >>>>> >>>>> (I cannot split into more jars, long story...) >>>>> >>>> >>>> Does that limitation apply to your development set up, or only to your >>>> runtime environment? In the latter case, you could use e.g. the Maven >>>> assembly:single command to put everything in a single jar: >>>> https://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html >>>> >>>> Or the Maven shade plugin: >>>> https://maven.apache.org/plugins/maven-shade-plugin/ >>>> >>>> >>>>> It's a big limitation that jooq requires compiled classes to generate >>>>> it's own objects (to make it work I can't generate jooq from jpa, but I've >>>>> got to do it via db directly, but I've got a lot of issue about this, like >>>>> circular dependency issue,...) >>>>> >>>> >>>> Hmm, that's really a class loading issue, not strictly related to jOOQ. >>>> Perhaps, the JPADatabase could use in-memory compilation for those >>>> entities, but that would be rather difficult to get right in more complex >>>> project setups, where the entities have external dependencies. >>>> >>>> >>>>> I'm wondering if jooq-jpa entities generator could be an apt one, like >>>>> others i.e. querydsl-jpa, JPAMetaModelEntityProcessor. These ones are >>>>> perfectly integrated in my scenario. >>>>> >>>>> What do you think about it? Are there some impedements I cant' see >>>>> about it? >>>>> >>>> >>>> It's a matter of priorities and a question whether the can of worms >>>> called APT should be opened. Perhaps it can be done, indeed. I've created a >>>> feature request for this: >>>> https://github.com/jOOQ/jOOQ/issues/6945 >>>> >>>> Thanks, >>>> Lukas >>>> >>> -- >>> 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/d/optout. >>> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "jOOQ User Group" group. >> To unsubscribe from this topic, visit https://groups.google.com/d/to >> pic/jooq-user/y4Xd4mzJtUQ/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > -- > 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/d/optout. > -- 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/d/optout.
