Hi Mark, I'm not sure which change in 1.2.1 would have affected the PCEnhancer in this way. I've seen similar problems with the tmpClassLoader specifically with the IBM JRE. Setting tmpClassloader = false didn't cause any problems for me.
-mike On Thu, Apr 2, 2009 at 2:59 AM, Mark Struberg <[email protected]> wrote: > > If you like to try it out you can download it from my git repo > > $> git clone http://ns1.backwork.net/git/openjpa-maven-plugin.git > > If there are no objections, then I'll commit the changes to the apache repo > tomorrow. > > > LieGrue, > strub > > --- Mark Struberg <[email protected]> schrieb am Do, 2.4.2009: > > > Von: Mark Struberg <[email protected]> > > Betreff: using the tmpClassLoader > > An: [email protected] > > Datum: Donnerstag, 2. April 2009, 9:40 > > > > Hi! > > > > I'm currently extending the openjpa-maven-plugin to be > > useful for openjpa-1.2.1 > > > > So while updating I had a problem with one of my projects > > which uses the following structure: > > > > --+- pom.xml > > |-api/pom.xml > > | \- public interface > > MyEntityInterface { > > | public > > static enum MessageChannel { MMS, SMS }; > > \-impl/pom.xml > > \- @Entity public class MyEntityImpl > > { > > private > > MessageChannel channel; > > > > In this case the PCEnhancer fails since openjpa-1.2.1 (no > > problems with 1.2.0 and 1.1.0 though) since the enum > > 'MessageChannel' cannot be found on the classpath. > > > > I now provide a 'tmpClassLoader' property in the > > openjpa-maven-plugin which defaults to 'false' and like to > > ask if this default is ok for most usecases, or if there are > > any objections? > > > > txs and LieGrue, > > strub > > > > > > > > > > > > > > > >
