> the first compilation (and therefore class generation) would kill that problem if it was generated next to > annotated class.
How will X.java be compiled to X.class if it refers to non-existent X_ -- even for the first time? My first guess to resolve such circularity will be to take into compiler rounds and annotation processor dialog -- which, current OpenJPA annotation processor does not. By the way, there is an openjpa example Ant script of generating these canonical classes [1]. The maven build kicks in this Ant build script -- (of course, this case does not involve circularity) [1] http://fisheye6.atlassian.com/browse/openjpa/trunk/openjpa-examples/openbooks/build.xml?r=HEAD ----- Pinaki -- View this message in context: http://openjpa.208410.n2.nabble.com/Generation-of-Canonical-MetaModel-Classes-with-Maven-tp5424291p5433982.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
