Am Donnerstag, 5. Juli 2012 18:43:52 UTC+2 schrieb Lukas Eder: > 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. >
1. Let's assume that you have a tool to modify the source in the way you want (this tool doesn't exist, you *will* have to write it first). Now you will have two source trees: The original and the transformed sources, right? In Eclipse, you will want to edit the **original** sources, right? In Maven, you will want to **compile** the **transformed** sources. When you open the project in Eclipse, m2e will look at the POM file and see "Hey, you want to compile **transformed** sources, so I'll set the source folders to the **transformed path**" If you change these paths to the **original sources**, m2e will complain "Project configuration is out of date. I won't let your compile that" -> Does not compute. 2. You have a tool to transform the sources. Instead of trying to do everything in a single project, you do: a) copy project to a new path b) transform copied sources in src/*/java c) Maybe add a qualifier "oracle" to the POM d) Let Maven compile it -> All problems solved. But you don't want to do that because "it's impossible" which means -> no solution. Regards, A. Digulla
