On May 22, 2012, at 11:41 PM, Steve Ebersole wrote: > This transition from "Configuration metadata" to "new Metadata" is just > that.. a transition. I'd really rather not spend a lot of time > developing testing extensions for dealing with the transitory nature of > this.
+1 I also cannot imagine that we can keep both code paths (new and old configuration/metadata) working for ever. At some stage we will have to wire up the new stuff for good and I don't think this is possible without breaking old code and tests. It might be a good idea to have to checkouts. One with the current HEAD of the metamodel work and one with the old code still in place. Instead of doing everything on one checkout work in two different checkouts with two IDE windows etc. This is probably even more effective, since now you can really compare things side by side. I am not doing this yet, since in the current state of the metamodel the test targeting just the metamodel are independent of any settings (as Steve already pointed out). --Hardy _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev