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 2019/01/07 16:40:00 UTC
[jira] [Commented] (SLING-8204) Rename maven-sling-plugin to
sling-maven-plugin
[ https://issues.apache.org/jira/browse/SLING-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736034#comment-16736034 ]
Konrad Windszus commented on SLING-8204:
----------------------------------------
There was once a discussion on the mailing list (or in the context of a JIRA issue) about this and the outcome was not to do it. I don’t remember the details though.
> Rename maven-sling-plugin to sling-maven-plugin
> -----------------------------------------------
>
> Key: SLING-8204
> URL: https://issues.apache.org/jira/browse/SLING-8204
> Project: Sling
> Issue Type: New Feature
> Components: Tooling
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Major
> Fix For: Maven Sling Plugin 2.3.10
>
>
> to avoid this maven build warning/error:
> {noformat}
> [ERROR]
> Artifact Ids of the format maven-___-plugin are reserved for
> plugins in the Group Id org.apache.maven.plugins
> Please change your artifactId to the format ___-maven-plugin
> In the future this error will break the build.
> {noformat}
> we need to rename the plugin from {{maven-sling-plugin}} to {{sling-maven-plugin}}.
> to still support builds with the old coordinates and support things like automatic dependency update checks we will publish a relocate pom using the old coordinate pointing to the new ones.
> this relocate pom will be contained in the same git repository as the sling-maven-plugin itself, and will be released with each new release.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)