sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Bosschaert (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (SLING-8213) Not possible to specify wildcard handler property in Maven plugin
Date Tue, 29 Jan 2019 11:17:00 GMT

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

David Bosschaert reassigned SLING-8213:
---------------------------------------

    Assignee: David Bosschaert

> Not possible to specify wildcard handler property in Maven plugin
> -----------------------------------------------------------------
>
>                 Key: SLING-8213
>                 URL: https://issues.apache.org/jira/browse/SLING-8213
>             Project: Sling
>          Issue Type: Bug
>          Components: Feature Model
>    Affects Versions: slingfeature-maven-plugin 0.8.0
>            Reporter: David Bosschaert
>            Assignee: David Bosschaert
>            Priority: Major
>             Fix For: slingfeature-maven-plugin 0.8.2
>
>
> The custom merge handlers executed during aggregation can be configured using {{handlerConfiguration}}
tags in the slingfeature-maven-plugin configuration.
> They can be configured on a per-plugin basis (plugin-name needs to be specified) or with
a wildcard.
> Currently the way to specify configuration that needs to be passed to all plugins is
by specifying {{*}} as the name, in the case of the maven plugin, the name is specify as an
XML tag.
> However {code}<*>{code} is not a valid XML tag and the pom will not parse with
such a tag, so using {{*}} as the wildcard is an unfortunate choice.
> We need to fix this so that wildcards can be specified in the pom.xml



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

Mime
View raw message