Ok, i see - then this has to be made very clear in the names, artifactids and the documentation. As artifactids of existing plugins can't be changed without any impact for the enduser (we don't have an alias system), this should at least be done for new ones. So then yes I think renaming should be fine (this was done for other plugins too) - maybe add a comment to the docu about the original name. Domi
> Am 04.02.2016 um 20:02 schrieb Tomas Bjerre <tomas.bjerr...@gmail.com>: > > When responding to this, you should know that "Bitbucket" and "Bitbucket > Server" are two different products, with different API:s. > > Get commits from Bitbucket: > https://confluence.atlassian.com/bitbucket/commits-or-commit-resource-389775478.html#commitsorcommitResource-GETacommitslistforarepositoryorcomparecommitsacrossbranches > > Get commits from Bitbucket Server: > https://developer.atlassian.com/static/rest/bitbucket-server/4.3.1/bitbucket-rest.html#idp2523328 > > Browse the API:s and you will see more examples. > > In my opinion, the naming is confusing. But that is a decision made by > Atlassian and nothing we can change. We can reduce the confusion by renaming > the stash-plugins to bitbucket-server-plugins. Because as more and more users > move to Bitbucket Server, people will forget that it was once called Stash. > > > 2016-02-04 16:39 GMT+01:00 domi <d...@fortysix.ch>: >> not sure about this, there are already a couple of bitbucket plugins and all >> of these address the hosted service bitbucket. >> /Domi >> >> >>> On 04 Feb 2016, at 16:38, Tomas Bjerre <tomas.bjerr...@gmail.com> wrote: >>> >>> Now that "Atlassian Stash" has changed name to "Atlassian Bitbucket >>> Server", perhaps some of the plugins >>> (https://github.com/jenkinsci?utf8=%E2%9C%93&query=stash) should also >>> change name. Or they can all be merged into 1 single plugin "Bitbucket >>> Server plugin". What do you think? >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to jenkinsci-dev+unsubscr...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/3c33d9b6-8b8a-490e-83f6-9bc424de2bbf%40googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Jenkins Developers" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-dev/ZZNVeE6mdA0/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> jenkinsci-dev+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/9F4305C0-80FF-4180-B7AD-9B4C4BB61FBD%40fortysix.ch. >> >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAK89W5KKNePJphN6BgN1_nR6cGiDwYnnJmoJT4MwoBrGg8vpNQ%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CC39C8AA-D251-44A0-B307-51A2DE15F05B%40fortysix.ch. For more options, visit https://groups.google.com/d/optout.
