RE: rename sling-maven-sling-plugin git repo?
ah, ok - than we can go with sling-maven-plugin. i've opened a ticket to do the rename [1]. stefan [1] https://issues.apache.org/jira/browse/INFRA-17653 >-Original Message- >From: Robert Munteanu [mailto:romb...@apache.org] >Sent: Tuesday, January 15, 2019 9:27 AM >To: dev@sling.apache.org >Subject: Re: rename sling-maven-sling-plugin git repo? > >Hi Stefan, > >On Mon, 2019-01-14 at 19:53 +, Stefan Seifert wrote: >> unfortunately it's not possible to create a new gitbox repo named >> "sling-sling-maven-plugin" because the form validation thinks the >> double prefix was not intended. > >Initially we only added the 'sling-' prefix if it was missing, see [0], >and our git at sling page says: > >"Append sling- to the artifact id if not there ( required by ASF infra >conventions )" > >So we don't have to add the double sling prefix, e.g. sling-sling- >maven-plugin, unless you think this is necessary. > >Thanks, > >Robert > > >[0]: https://github.com/apache/sling-tooling- >scm/blob/6ec198081787ac90c6d662d51e99b8fa312e36da/scripts/migrate-to- >git.sh#L88-L92 >
Re: rename sling-maven-sling-plugin git repo?
Hi Stefan, On Mon, 2019-01-14 at 19:53 +, Stefan Seifert wrote: > unfortunately it's not possible to create a new gitbox repo named > "sling-sling-maven-plugin" because the form validation thinks the > double prefix was not intended. Initially we only added the 'sling-' prefix if it was missing, see [0], and our git at sling page says: "Append sling- to the artifact id if not there ( required by ASF infra conventions )" So we don't have to add the double sling prefix, e.g. sling-sling- maven-plugin, unless you think this is necessary. Thanks, Robert [0]: https://github.com/apache/sling-tooling-scm/blob/6ec198081787ac90c6d662d51e99b8fa312e36da/scripts/migrate-to-git.sh#L88-L92
Re: rename sling-maven-sling-plugin git repo?
This should be possible via INFRA. Compare e.g. with https://issues.apache.org/jira/browse/INFRA-16017?filter=-4=project%20%3D%20INFRA%20AND%20text%20~%20%22rename%20git%22%20order%20by%20created%20DESC > Am 14.01.2019 um 20:53 schrieb Stefan Seifert : > > should we rename the github repo as well to "sling-sling-maven-plugin"? > > it would > a) be more consistent and > b) fix auto-generated github links like on the download page [1] which is > currently broken > > i'm not sure if renaming a github & gitbox is possible (at least there is no > self-service tool for it). another option would be to create a new repo, > clone the content and delete the old one. unfortunately it's not possible to > create a new gitbox repo named "sling-sling-maven-plugin" because the form > validation thinks the double prefix was not intended. > > stefan > > [1] https://sling.apache.org/downloads.cgi > >
rename sling-maven-sling-plugin git repo?
should we rename the github repo as well to "sling-sling-maven-plugin"? it would a) be more consistent and b) fix auto-generated github links like on the download page [1] which is currently broken i'm not sure if renaming a github & gitbox is possible (at least there is no self-service tool for it). another option would be to create a new repo, clone the content and delete the old one. unfortunately it's not possible to create a new gitbox repo named "sling-sling-maven-plugin" because the form validation thinks the double prefix was not intended. stefan [1] https://sling.apache.org/downloads.cgi
