java.lang.ClassNotFoundException: org.apache.maven.model.io.xpp3.MavenXpp3WriterEx happens with s2i builds

Issue

During s2i buld, the following ERROR happens.

[INFO] --- maven-help-plugin:3.2.0:evaluate (default-cli) @ swagger-annotations ---
 ....
[ERROR]
java.lang.ClassNotFoundException: org.apache.maven.model.io.xpp3.MavenXpp3WriterEx
at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass (SelfFirstStrategy.java:50)
at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass (ClassRealm.java:271)
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass (ClassRealm.java:247)
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass (ClassRealm.java:239)
at java.lang.Class.forName0 (Native Method)
at java.lang.Class.forName (Class.java:398)
at org.apache.commons.lang3.ClassUtils.getClass (ClassUtils.java:993)
at org.apache.commons.lang3.ClassUtils.getClass (ClassUtils.java:1059)
at org.apache.commons.lang3.ClassUtils.getClass (ClassUtils.java:1042)
at org.apache.maven.plugins.help.EvaluateMojo.addAlias (EvaluateMojo.java:542)
at org.apache.maven.plugins.help.EvaluateMojo.addAlias (EvaluateMojo.java:491)
at org.apache.maven.plugins.help.EvaluateMojo.getXStream (EvaluateMojo.java:455)
at org.apache.maven.plugins.help.EvaluateMojo.toXML (EvaluateMojo.java:420)
at org.apache.maven.plugins.help.EvaluateMojo.handleResponse (EvaluateMojo.java:381)
at org.apache.maven.plugins.help.EvaluateMojo.execute (EvaluateMojo.java:214)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)

But s2i build succeeded and the generated kjar have been deployed and rules could be executed even though this error happened.
Why does this error happen and how to avoid this?