[
https://issues.apache.org/jira/browse/MNG-5949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060851#comment-15060851
]
Karl Heinz Marbaise commented on MNG-5949:
------------------------------------------
In general you are right, but i had a case where a script which ran on the
jenkins server via cron (and accidentally) changed permissions of parent folder
(this took me more than a week to find the cause).....so i'm just asking to be
sure..So next step... which version is selected in the Job for Maven? Are you
using {{.mvn}} folder configuration? BTW: Are you just calling {{mvn clean
deploy}} ? and in your case {{mvn -T2 clean deploy}} Are you calling maven
from root of the project? Is this project a multi module build (I assume
so)...Can you give also the exact Jenkins version? An other thing is
interesting that i found a
[issue|https://issues.jenkins-ci.org/browse/JENKINS-29120] which contains
exactly those references to those classes
{{hudson.remoting.UserRequest.perform(UserRequest.java:99)}}...
> NPE when running with -T2 under Jenkins
> ---------------------------------------
>
> Key: MNG-5949
> URL: https://issues.apache.org/jira/browse/MNG-5949
> Project: Maven
> Issue Type: Bug
> Components: core
> Affects Versions: 3.3.1, 3.3.3, 3.3.9
> Environment: Linux x64, JDK 8, Jenkins
> Reporter: Axel Fontaine
>
> When running single threaded everything works fine. When I enable -T2 the
> resource plugin fails to create the output directory of the second module due
> to this NPE:
> java.lang.NullPointerException
> at
> org.apache.maven.execution.MavenSession.getPluginContext(MavenSession.java:195)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:561)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:121)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> 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:116)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:181)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
