You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/03/17 13:03:00 UTC

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

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

Konrad Windszus updated JCRVLT-432:
-----------------------------------
    Fix Version/s:     (was: package-maven-plugin-1.3.0)

> 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
>
> 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.20.1#820001)