• 6
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 02-11-2018

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future, i.e. in next 6 months.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.

      Atlassian will keep the issue open and continue to watch this issue for the further updates.

      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 02-11-2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future, i.e. in next 6 months. Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will keep the issue open and continue to watch this issue for the further updates. Thank you, Ignat Alexeyenko Jira Bugmaster

      Summary

      The public atlassian maven repository (https://maven.atlassian.com/public/) does not provide javadoc jars for jira-api. We need this Javadoc as jar in the repo to efficiently code plugins.

      Expected results

      The documentation states that there should be javadoc jars for all closed-source components (see below).

      "The Atlassian public repository contains all artifacts necessary to build a plugin for our products. It contains binaries, source and javadoc of our opensource components, and binaries and javadoc for our closed-source components. Anyone can read from this repository. Only Atlassian staff can write to it."

      Excerpt from:
      https://developer.atlassian.com/docs/advanced-topics/working-with-maven/atlassian-maven-repositories?continue=https%3A%2F%2Fdeveloper.atlassian.com%2Fdocs%2Fadvanced-topics%2Fworking-with-maven%2Fatlassian-maven-repositories&application=dac

      Workaround

      There is currently no workaround for this.

            [JRASERVER-42338] Maven repository does not provide javadoc jars for jira-api

            Just wanted to let you know that out developers are still disappointed. This does not and will never have many votes since every developer using the api slowly succumbs to a death by a thousand papercuts. Maybe you could fix this as part of some clean-up epic that collects some low effort fixes?

            Jörg Sesterhenn added a comment - Just wanted to let you know that out developers are still disappointed. This does not and will never have many votes since every developer using the api slowly succumbs to a death by a thousand papercuts. Maybe you could fix this as part of some clean-up epic that collects some low effort fixes?

            Come on guys, it's not 2006 anymore, where we were all fine with importing docs manually. Don't wait for the votes, just do it please.

            Deleted Account (Inactive) added a comment - Come on guys, it's not 2006 anymore, where we were all fine with importing docs manually. Don't wait for the votes, just do it please.

            I already did. It still has only two votes though.

            Hannes Niederhausen added a comment - I already did. It still has only two votes though.

            If you want this to happen please upvote to indicate urgency and thus increase pressure.

            Jörg Sesterhenn added a comment - If you want this to happen please upvote to indicate urgency and thus increase pressure.

            Still no update? How is this such a big issue?

            Hannes Niederhausen added a comment - Still no update? How is this such a big issue?

            Hi dr.pymote510566881,

            This is already in our short-term backlog. Unfortunately, we have no been able to assign it to a developer yet, but we aim to do this as soon as we are able to.

            Please do watch the issue for further updates, we will change its status as soon as more information is available.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi dr.pymote510566881 , This is already in our short-term backlog. Unfortunately, we have no been able to assign it to a developer yet, but we aim to do this as soon as we are able to. Please do watch the issue for further updates, we will change its status as soon as more information is available. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            Any updates on this? Still there are no javadocs / sources attached

            Matthias Mueller added a comment - Any updates on this? Still there are no javadocs / sources attached

            Hi joerg.sesterhenn,

            Thanks for raising this with us, after discussing this matter internally with several people in the team, I see no reason for the api's javadoc not to be available via maven.

            I will schedule this in our short-term backlog so we can correct this.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi joerg.sesterhenn , Thanks for raising this with us, after discussing this matter internally with several people in the team, I see no reason for the api's javadoc not to be available via maven. I will schedule this in our short-term backlog so we can correct this. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            I found statements that the API documentation is not avaiable for download:
            https://confluence.atlassian.com/display/JIRA/API+Documentation

            Please note, the API documentation is not available for download.

            https://answers.atlassian.com/questions/153983/where-can-i-find-the-jira-api-javadoc-jar

            Javadocs are not available for downloading as a .jar file, it's only available online at http://docs.atlassian.com/,

            Would you care to explain why???

            This is really demotivating for plugin developers. I don't want to jump between my browser and IDE all the time! Would you?
            I see no reason why you should not provide Javadoc for the API as jar.

            Jörg Sesterhenn added a comment - I found statements that the API documentation is not avaiable for download: https://confluence.atlassian.com/display/JIRA/API+Documentation Please note, the API documentation is not available for download. https://answers.atlassian.com/questions/153983/where-can-i-find-the-jira-api-javadoc-jar Javadocs are not available for downloading as a .jar file, it's only available online at http://docs.atlassian.com/ , Would you care to explain why??? This is really demotivating for plugin developers. I don't want to jump between my browser and IDE all the time! Would you? I see no reason why you should not provide Javadoc for the API as jar.

            There is javadoc here:
            https://developer.atlassian.com/static/javadoc/jira/6.0.4/reference/packages.html

            But as I said, it would be far more efficient to code, if you provided this through maven.

            Jörg Sesterhenn added a comment - There is javadoc here: https://developer.atlassian.com/static/javadoc/jira/6.0.4/reference/packages.html But as I said, it would be far more efficient to code, if you provided this through maven.

              Unassigned Unassigned
              0c911a92da49 Jörg Sesterhenn
              Affected customers:
              7 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated: