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

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

    [ https://issues.apache.org/jira/browse/SLING-9794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208620#comment-17208620 ] 

A. J. David Bosschaert commented on SLING-9794:
-----------------------------------------------

I think this is caused by the fact that it uses {{project.getDependencyArtifacts()}} sometimes, which does not seem to set the {{file}} attribute. One option would be to use Aether to resolve the artifacts, as that seems to work consistently.

> 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.



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