[jira] [Resolved] (SLING-11536) Remove wrong LifecycleMapping metadata

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

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

Konrad Windszus resolved SLING-11536.
-------------------------------------
    Resolution: Fixed

Fixed in https://github.com/apache/sling-maven-plugin/commit/eeca5fb6fc5f280a7043638b97f9ab6c8692e275.

> Remove wrong LifecycleMapping metadata
> --------------------------------------
>
>                 Key: SLING-11536
>                 URL: https://issues.apache.org/jira/browse/SLING-11536
>             Project: Sling
>          Issue Type: Bug
>          Components: Maven Plugins and Archetypes
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Sling Maven Plugin 3.0.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The sling-maven-plugin contains Plexus component metadata for a {{org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping}} with role {{assembly}} (https://github.com/apache/sling-maven-plugin/blob/e5da7210376d1951c2fa4ce76f69cb7632cee36f/sling-maven-plugin/src/main/resources/META-INF/plexus/components.xml#L20).
> Although this only is active if {{sling-maven-plugin}} is used with {{<extensions>true</extensions>}} it is wrong in any case, as it defines a mapping for packaging "assembly" and also only binds Maven default plugin goals.
> As the {{sling-maven-plugin}} doesn't do any packaging nor defines a custom packaging, providing a custom {{DefaultLifecycleMapping}} is not necessary and in the worst case might have negative side-effects.



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