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 2023/08/02 15:50:00 UTC

[jira] [Resolved] (JCRVLT-715) Content Package with classifier potentially installed/deployed with wrong extension

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

Konrad Windszus resolved JCRVLT-715.
------------------------------------
    Resolution: Fixed

Fixed in https://github.com/apache/jackrabbit-filevault-package-maven-plugin/commit/e78d3b4d28f6de8ebd0f83f7a58d5e3e25edc57e.

> Content Package with classifier potentially installed/deployed with wrong extension
> -----------------------------------------------------------------------------------
>
>                 Key: JCRVLT-715
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-715
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>          Components: package maven plugin
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: package-maven-plugin-1.3.6
>
>
> The "package" goal attaches the content package as secondary artifact when a classifier is used (https://github.com/apache/jackrabbit-filevault-package-maven-plugin/blob/58a395fdbfccbecb772be2cec2b9e347d34d0d0f/src/main/java/org/apache/jackrabbit/filevault/maven/packaging/mojo/VaultMojo.java#L568). This uses the type of the underlying Maven project (which may be different from content-package/zip), so you might end up with content packages with the wrong extension in the local/remote repo.



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