On Monday, April 28, 2014 7:30:23 AM UTC-7, Lukas Eder wrote:
>
> ...
>
> Did you encounter this issue with jOOQ 3.3, i.e. with the latest version?
>
Ah, you know, what? I indeed encountered that bug with an older version
(which is also why I didn't see that separate name mangling issue at
first). I had already worked around the relative directory issue before
realizing I was using an older version.
(I'll note that the online example indicates an older version, which was
why I wound up with the wrong version in the first place. I realize that
it's hard to keep all the documentation up-to-date. I assume that the
various Maven plugins documentations use some sort of expression evaluation
to keep version numbers up-to-date.)
In any case, I think I'll keep the ${project.build.directory} in my POM as
it doesn't requirement me to hard-code the targets directory.
Thanks.
Garret
--
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.
