Closed GoogleCodeExporter closed 9 years ago
I'm going to look into what we can do for Datanucleus, definitely an Archetype,
and I'll look into what else we can do to make it easy to use.
Original comment by matts...@google.com
on 18 Dec 2012 at 8:14
Original comment by matts...@google.com
on 18 Dec 2012 at 8:14
Check out the appengine:enhancer goal and see if that does what you want.
Original comment by matts...@google.com
on 21 Mar 2013 at 6:17
Can the enhancer goal also be executed part of the devserver and update targets?
Original comment by marceloverdijk
on 30 Mar 2013 at 5:04
This works:
<plugin>
<groupId>com.google.appengine</groupId>
<artifactId>appengine-maven-plugin</artifactId>
<version>${com.google.appengine.version}</version>
<configuration>
<disableUpdateCheck>true</disableUpdateCheck>
<jvmFlags>
<jvmFlag>-javaagent:${env.REBEL_HOME}/jrebel.jar</jvmFlag>
<jvmFlag>-Ddatastore.backing_store=${project.basedir}/local_db.bin</jvmFlag>
<jvmFlag>-Ddatastore.default_high_rep_job_policy_unapplied_job_pct=20</jvmFlag>
</jvmFlags>
<useJava7>true</useJava7>
</configuration>
<executions>
<execution>
<phase>compile</phase>
<goals>
<goal>enhance</goal>
</goals>
</execution>
</executions>
</plugin>
Original comment by marceloverdijk
on 2 Apr 2013 at 1:22
Maybe good to note that when you are using the aspectj-maven-plugin in your
project, this plugin needs to be defined before the appengine-maven-plugin in
the <plugins> section. Otherwise the aspectj-maven-plugin overrides the
enhanced 'datanucleus' classes.
Original comment by marceloverdijk
on 4 Apr 2013 at 7:24
Alternatively hook the enhance goal into the process-classes lifecycle:
<phase>process-classes</phase>
Original comment by marceloverdijk
on 4 Apr 2013 at 12:26
Original issue reported on code.google.com by
marceloverdijk
on 17 Dec 2012 at 10:13