[jira] [Assigned] (MNG-8389) User/project/installation settings file locations not available

["Tamas Cservenak (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MNG-8389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tamas Cservenak reassigned MNG-8389:
------------------------------------

    Assignee: Tamas Cservenak

> User/project/installation settings file locations not available
> ---------------------------------------------------------------
>
>                 Key: MNG-8389
>                 URL: https://issues.apache.org/jira/browse/MNG-8389
>             Project: Maven
>          Issue Type: Bug
>          Components: Command Line
>    Affects Versions: 4.0.0-rc-1
>            Reporter: Guillaume Nodet
>            Assignee: Tamas Cservenak
>            Priority: Major
>             Fix For: 4.0.0-rc-2
>
>
> When building Karaf with 4.0.0-rc-1, the following error occurs in ITs:
> {code}
> [INFO] Caused by: java.lang.NullPointerException: Cannot invoke "java.io.File.exists()" because the return value of "org.apache.maven.execution.MavenExecutionRequest.getUserSettingsFile()" is null
> [INFO]     at org.apache.karaf.tooling.VerifyMojo.execute(VerifyMojo.java:198)
> [INFO]     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:144)
> [INFO]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2(MojoExecutor.java:339)
> [INFO]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute(MojoExecutor.java:310)
> [INFO]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:214)
> [INFO]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:179)
> [INFO]     at org.apache.maven.lifecycle.internal.MojoExecutor$1.run(MojoExecutor.java:168)
> [INFO]     at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute(DefaultMojosExecutionStrategy.java:39)
> [INFO]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:165)
> [INFO]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:107)
> [INFO]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:73)
> [INFO]     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:60)
> [INFO]     at org.apache.maven.lifecycle.internal.DefaultLifecycleStarter.execute(DefaultLifecycleStarter.java:123)
> [INFO]     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:311)
> [INFO]     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:225)
> [INFO]     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:149)
> [INFO]     at org.apache.maven.cling.invoker.mvn.MavenInvoker.doExecute(MavenInvoker.java:497)
> [INFO]     at org.apache.maven.cling.invoker.mvn.MavenInvoker.execute(MavenInvoker.java:99)
> [INFO]     at org.apache.maven.cling.invoker.mvn.MavenInvoker.execute(MavenInvoker.java:89)
> [INFO]     at org.apache.maven.cling.invoker.LookupInvoker.doInvoke(LookupInvoker.java:141)
> [INFO]     at org.apache.maven.cling.invoker.LookupInvoker.invoke(LookupInvoker.java:113)
> [INFO]     at org.apache.maven.cling.ClingSupport.run(ClingSupport.java:64)
> [INFO]     at org.apache.maven.cling.MavenCling.main(MavenCling.java:51)
> [INFO]     at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> [INFO]     at java.lang.reflect.Method.invoke(Method.java:580)
> [INFO]     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:255)
> [INFO]     at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:201)
> [INFO]     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:361)
> [INFO]     at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:314)
> {code}
> The reason is that cling does not seem to update the MavenExecutionRequest with the computed values for user/project/installation settings.  That was done by SettingsXmlConfigurationProcessor with the old CLI.  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)