> What time? The interfaces could be generated automatically from the > annotations.
If you do this, and also implement an automatic BNF -> interfaces generator as discussed at the JUGS, I'm sure you could make some money with a patent on it :-) >> > - Strip the code inline -> That would either confuse Eclipse (you can't >> > edit >> > the original source code anymore) or Maven (generating source code into >> > the >> > folder src/*/java isn't defined behavior). >> >> I'm not sure what that means. > > Some of the Maven plugins will get confused when you change the files in > src/*/java after you started Maven. I don't know which ones but changing > those files is asking for trouble. Eventually, you will run into problems > because no one expects that this could happen. OK. I'll verify this on Stack Overflow. It doesn't sound like a very surprising idea to me. But as I said, I don't know Maven enough. This is the question: http://stackoverflow.com/questions/11348840/use-maven-to-pre-process-source-code-that-is-going-to-be-built-with-maven > Which means you will need to copy the jOOQ sources into a different folder > (say, "template/") and generate the sources from there into > "target/generated-sources/". "template/" can't be a source folder (neither > m2e nor Maven support this). Which would mean you couldn't edit the original > sources in the Java editor anymore. This isn't about modifying original sources. This is about modifying build deliverables. The original sources should stay the same. But when you link such a modified jOOQ from your projects, you wouldn't see the original sources anymore, because the linked .jar files would only contain the modified sources / javadocs / bytecode. > My conclusion: Nice idea, impossible to implement in Java. Let's not give up early Cheers Lukas
