To elaborate, here's the Exception with --debug turned on:

[DEBUG] Trace
org.apache.maven.BuildFailureException: Compilation failure
error: Exception thrown while constructing Processor object: javax/jdo/
PersistenceManagerFactory
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
580)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:
5 00)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:
479)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.ja
va:331)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:
292)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:
142)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
336)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
129)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.CompilationFailureException:
Compilation failure
error: Exception thrown while constructing Processor object: javax/jdo/
PersistenceManagerFactory
        at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:
516)
        at
org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:
453)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
559)
        ... 16 more

Any ideas, anyone?

On Mar 8, 11:55 am, tkinsella <troy.kinse...@shaw.ca> wrote:
> Pardon me, I didn't realize 2.0 was not supported. However, using the
> latest 1.x version results in the same error for me.
>
> Here's my new build plugins config:
>
> <plugin>
>                 <groupId>org.datanucleus</groupId>
>                 <artifactId>maven-datanucleus-plugin</artifactId>
>                 <version>1.1.4</version>
>                 <configuration>
>                     <log4jConfiguration>${basedir}/log4j.properties</
> log4jConfiguration>
>                     <verbose>true</verbose>
>                     <persistenceUnitName>my_persistence_unit_name</
> persistenceUnitName>
>                     <enhancerName>ASM</enhancerName>
>                     <api>JPA</api>
>                 </configuration>
>                 <executions>
>                     <execution>
>                         <phase>process-classes</phase>
>                         <goals>
>                             <goal>enhance</goal>
>                         </goals>
>                     </execution>
>                 </executions>
>             </plugin>
>
> I have the following in repositories and pluginRepositories,
> respectively:
>
> <repository>
>     <id>DataNucleus_Repos2</id>
>     <name>DataNucleus Repository</name>
>     <url>http://www.datanucleus.org/downloads/maven2</url>
> </repository>
>
> ...
> <pluginRepository>
>     <id>DataNucleus_2</id>
>     <url>http://www.datanucleus.org/downloads/maven2</url>
> </pluginRepository>
>
> And running mvn install, again, produces the following output:
>
> 8-Mar-2010 11:44:21 AM org.datanucleus.enhancer.DataNucleusEnhancer
> <init>
> INFO: DataNucleus Enhancer : Using ClassEnhancer "ASM" for API "JDO"
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Compilation failure
> error: Exception thrown while constructing Processor object: javax/jdo/
> PersistenceManagerFactory
>
> I guess the root of my question is: how do I get past this problem?
> Thanks for the responses so far, and thanks in advance for any further
> advice!
>
> Troy
>
> On Mar 8, 7:32 am, datanucleus <andy_jeffer...@yahoo.com> wrote:
>
> > How can you use v2.0 of the DN maven2 plugin when GAE/J only supports
> > v1.x ?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

Reply via email to