[jira] [Resolved] (SLING-9794) Content package artifacts found by maven plugin don't always have their 'file' attribute set

["David Bosschaert (Jira)" <ji...@apache.org>]

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

David Bosschaert resolved SLING-9794.
-------------------------------------
    Resolution: Fixed

> Content package artifacts found by maven plugin don't always have their 'file' attribute set
> --------------------------------------------------------------------------------------------
>
>                 Key: SLING-9794
>                 URL: https://issues.apache.org/jira/browse/SLING-9794
>             Project: Sling
>          Issue Type: Bug
>          Components: Content-Package to Feature Model Converter
>    Affects Versions: Feature Model Converter Plugin 1.0.4
>            Reporter: A. J. David Bosschaert
>            Assignee: A. J. David Bosschaert
>            Priority: Major
>             Fix For: Feature Model Converter Plugin 1.0.6
>
>
> The Content Package to Feature Model plugin looks up content packages from the maven dependencies in {{ContentPackage.getMatchingArtifacts()}}. 
> However this mechanism doesn't always work fully, leaving the {{file}} attribute of the returned Artifacts {{null}}. 
> This later causes a NPE when the result is processed: 
> {code:java}
> Caused by: java.lang.NullPointerException
>     at org.apache.sling.cpconverter.maven.mojos.ConvertCPMojo.execute (ConvertCPMojo.java:238)
>     at com.adobe.aem.analyser.mojos.ConvertToFeatureModelMojo.execute (ConvertToFeatureModelMojo.java:46)
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
>     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:957)
>     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
>     at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
>     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:282)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)