[
https://issues.apache.org/jira/browse/SLING-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736038#comment-16736038
]
Stefan Seifert commented on SLING-8204:
---------------------------------------
are you sure? i was only aware of
https://lists.apache.org/thread.html/f058f8e2756cb0855121b21a3f7f6195dae426213d9f57ba4080ffa6@%3Cdev.sling.apache.org%3E
and i'm picking up the proposal [~olli] here, which worked quite well for the
relocation of osgi-mock and sling-mock already.
> 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)
