[jira] [Commented] (JCRVLT-432) Consolidate how to reference Maven dependencies from configuration parameters

["Konrad Windszus (Jira)" <ji...@apache.org>]

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

Konrad Windszus commented on JCRVLT-432:
----------------------------------------

The new parameter should be based on https://maven.apache.org/shared/maven-common-artifact-filters/.

> Consolidate how to reference Maven dependencies from configuration parameters
> -----------------------------------------------------------------------------
>
>                 Key: JCRVLT-432
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-432
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>          Components: package maven plugin
>    Affects Versions: package-maven-plugin-1.1.2
>            Reporter: Konrad Windszus
>            Priority: Major
>             Fix For: package-maven-plugin-1.1.8
>
>
> The following configuration entries might refer to Maven dependencies
> # embeddeds (http://jackrabbit.apache.org/filevault-package-maven-plugin/generate-metadata-mojo.html#embeddeds)
> # subPackages (http://jackrabbit.apache.org/filevault-package-maven-plugin/generate-metadata-mojo.html#subPackages)
> # dependencies (http://jackrabbit.apache.org/filevault-package-maven-plugin/generate-metadata-mojo.html#dependencies)
> # repositoryStructurePackages  (http://jackrabbit.apache.org/filevault-package-maven-plugin/validate-files-mojo.html#repositoryStructurePackages)
> Some allow a filter based approach on only artifactId others require giving at least both groupId and artifactId. This should be consolidated, so that referencing Maven dependencies works always the same way.



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