I was sent the url to the old velocity stuff and I see several thread safety issues in the (*really* old) version being used by m-r-r-p.

I checked out the latest version of velocity and all the problems I found were fixed there, so I think we'll just give it a shot.

Just make an issue under http://jira.codehaus.org/browse/MRRESOURCES and I'll push it through.


Kristian


Den 23.03.2011 23:29, 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]

Reply via email to