Pinaki Poddar wrote: > > 1. I think you are running into circular reference problem. > > 2. So please verify if is only a "maven" problem -- I am guessing that any > compilation (ant, command-line) should encounter the same problem. If not, > I have to think more about what is happening. > > 3. About -out/-s option to direct the output source code location : > Which exact version of openjpa is being used? > Do > $ java -jar /path/to/openjpa.jar > >> because I want to develop on a stable release. > OpenJPA trunk is a solid trunk. The changes injected are highly > monitored and continuously tested over a corpus of 4000+ tests. So > stability should not be a concern, surely not for development. Production > may be a different story from a support point of view. > >
1. and 2. Yes, there is something of a circulate reference. But, the first compilation (and therefore class generation) would kill that problem if it was generated next to annotated class. It would be available at the next compile run. Thinking-out-of-box: Maven allows attaching plugins and running goals (mojo) at any step of the compilation process. We could do this at the generate-sources step, which is before process-sources (and way before the compile step) For ant people, I understand they could do something similar (i.e., preprocessing very early in the compilation process). 3. Maven downloads the openjpa.jar from the specifications in my pom.xml. In my case, it is 2.0.0 for openjpa-all.jar. -- View this message in context: http://openjpa.208410.n2.nabble.com/Generation-of-Canonical-MetaModel-Classes-with-Maven-tp5424291p5433429.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
