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 2018/02/17 11:09:00 UTC

[jira] [Comment Edited] (JCRVLT-274) Package Maven Plugin: Support multiple types as filter within embedded section

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

Konrad Windszus edited comment on JCRVLT-274 at 2/17/18 11:08 AM:
------------------------------------------------------------------

To make it more consistent and flexible the same approach should be applied to {{classifier}}.


was (Author: kwin):
To make it more consistent and flexible the same approach should be applied to {{scope}} and {{classifier}}.

> Package Maven Plugin: Support multiple types as filter within embedded section
> ------------------------------------------------------------------------------
>
>                 Key: JCRVLT-274
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-274
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>          Components: package maven plugin
>    Affects Versions: package-maven-plugin-1.0.1
>            Reporter: Konrad Windszus
>            Priority: Major
>
> Currently the {{embeddeds}} complex parameter only allows the {{groupId}} or {{artifactId}} have complex pattern values. That would be useful as well for the {{type}} (which is currently just based on plain string equality) because bundles in general may either have type {{jar}} or {{bundle}}. Both make sense in this context, therefore it is probably useful to configure both types in a generic parent pom.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)