... Unfortunately, it looks like we've fallen into an impedance mismatch
trap between XSD, JAXB, XJC and Maven. Maven's understanding of XML is much
simpler than XSD's / JAXB's, which is why it couldn't read this particular
configuration. The way I see this, this can only be solved by incompatibly
changing the XSD for the matcher strategy to be configured as such:
<strategy>
<matchers>
<fields>
<field>
<expression>DUMMY</expression>
<fieldSetter><expression>DUMMY</expression></fieldSetter>
<fieldGetter><expression>DUMMY</expression></fieldGetter>
</field>
</fields>
</matchers>
</strategy>
Notice the additional <fields><field/></fields> indirection. This fix has
been implemented for the upcoming jOOQ 3.3.0 and won't be merged to jOOQ
3.2 because of the incompatibility of XSD changes. There will be a remark
in the jOOQ 3.2 manual indicating that the matcher strategy cannot be used
with the maven plugin.
2013/12/30 Lukas Eder <[email protected]>
>
>
>
> 2013/12/30 <[email protected]>
>
> Hello Lukas,
>>
>> I don't work as much as I'd like on my project right now, but what I
>> decided to do is to use my own Maven plugin and call
>> *GenerationTool.main(configuration)* by myself. It is still untested
>> yet, but I don't see why it wouldn't work.
>>
>> I didn't try to find why *jooq-codegen-maven* isn't working properly
>> though, sorry.
>>
>
> OK, no worries. I'll figure it out.
>
> Cheers
> 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/groups/opt_out.
