I had initially reported an issue with Maven 3.3.9, that was fixed with a merge request, this time we upgraded to Maven 3.5.0 and we are presented the same type of issue

I have seen Oleg reply pointing me to this patch but I don't think it is part of Maven-plugin 2.16 https://github.com/jenkinsci/maven-plugin/blob/master/src/main/java/hudson/maven/MavenBuild.java#L840-L847

I can confirm else that setting up 2 version of Maven in Jenkins and switching from 3.5.0 to 3.3.9 fixes the issue.
Established TCP socket on 38574
<===[JENKINS REMOTING CAPACITY]===>channel started
Executing Maven: -N -B -s /home/jenkins/config/settings_maven_integration.xml -f /home/jenkins/workspace/SDR_TRUNK_TEST_INTEGRATION/outillage/tests-integration/tests-services/pom.xml clean deploy -Pjenkins,integration,integration-deploiements-services,tests-soapui,tests-soapui-services
java.lang.NullPointerException
at jenkins.maven3.agent.Maven33Main.launch(Maven33Main.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:139)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
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)
Started by user ***
Finished: ABORTED
Set build name.