Pinaki, The culprit in my case was maven/m2eclipse which by default executes the maven builder on every change. This wasn't an issue at all related to openjpa other then it was a required step within the build.
While that default behavior can, and should, be modified. My experience was that it added confusion for developers who previously didn't have to know about byte code enhancement or even a maven build. -Andy On Tue, 2011-07-12 at 17:56 -0700, Pinaki Poddar wrote: > > even then that introduced a minute or two of build time in eclipse > How are you invoking build-time enhancement in Eclipse? > > > which without hackery insists on a full project build. > Who insists on a full project build on minor changes? > > ----- > Pinaki Poddar > Chair, Apache OpenJPA Project > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/Problems-with-load-time-enhancement-and-Spring-s-TomcatInstrumentableClassLoader-tp6554347p6577376.html > Sent from the OpenJPA Users mailing list archive at Nabble.com.
