The problem seems to be within velocity, or at least within the ancient version of velocity that's being used by the remote resources plugin.
The problem is that the version of plexus-velocity being used by remote-resources plugin is so old that I can't find the source anywhere (codehaus only has 1.1.4, m-r-r-p uses 1.1.3 and the latest is 1.1.8) If you just file an issue under remote resource plugin (http://jira.codehaus.org/browse/MRRESOURCES), I'll upgrade to 1.1.8 and publish a new snapshot version you can try. Kristian on., 23.03.2011 kl. 15.29 -0700, skrev David Jencks: > I've been trying out the parallel stuff in maven 3.0.3 and when it works it's > great. However I'm wondering what's going on here with this intermittent > error. I've never gotten this error bulding single threaded. > > https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html says the > maven-remote-resources-plugin 1.2 is threadsafe. However... > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-remote-resources-plugin:1.2:process (default) > on project assemblies: Error rendering velocity resource. > NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-remote-resources-plugin:1.2:process > (default) on project assemblies: Error rendering velocity resource. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167) > at > org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:164) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:680) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error rendering > velocity resource. > at > org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1212) > at > org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:519) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 13 more > Caused by: java.lang.NullPointerException > at > org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:831) > at > org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:440) > at > org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:419) > at > org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1125) > ... 16 more > > I ran with -T 4. It looks like there were 3 failures with this same stack > trace all in pom projects that aggregate subprojects. > > I don't have a lot of time to track down whats going on but might be able to > spend a little time given enough advice. > > thanks > david jencks > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
