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

[jira] [Resolved] (SLING-11534) uninstall goal: Allow to parameterize Bundle Symbolic Name/Resource Name directly

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

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

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

> uninstall goal: Allow to parameterize Bundle Symbolic Name/Resource Name directly
> ---------------------------------------------------------------------------------
>
>                 Key: SLING-11534
>                 URL: https://issues.apache.org/jira/browse/SLING-11534
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Sling Maven Plugin 3.0.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Currently the uninstall goal requires the parameter {{bundleFileName}} which is set to a default path which often reflects the artifact file name bound by the current project.
> In order to ease uninstalling arbitrary packages, it should be allowed to uninstall bundles by just giving their Bundle Symbolic Name (BSN) / file name.
> The file name is used for all deployment methods except for Web Console (to remove the same named resource from the repository), otherwise the BSN is used.
> The old way of determining the BSN from a given file should be used as fallback.



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