Skip to content

[Doc] Migrate C++ and Python client API docs generate processΒ #17917

Closed
apache/pulsar-site
#286

Description

@tisonkun

Search before asking

  • I searched in the issues and found nothing similar.

What issue do you find in Pulsar docs?

After #17724 moves pulsar-client-cpp and pulsar-client-python to new repository, the original doxygen-doc-gen.sh and pdoc generation process can break.

What is your suggestion?

We should investigate them and migrate if necessary.

The Python part should be done by:

Any reference?

@urfreespace @SignorMercurio @michaeljmarshall please take a look.

cc @Anonymitaet @momo-jun

Are you willing to submit a PR?

  • I'm willing to submit a PR!

Activity

  1. added
    doc-requiredYour PR changes impact docs and you will update later.
    on Oct 4, 2022
  2. Mini256 commented on Oct 25, 2022

    @Mini256

    When I installed the pulsar client according to the documentation, I found that the pulsar-client-cpp has been migrated, will this issue be used to track the issue of updating the repo link in the documentation?

    https://pulsar.apache.org/docs/client-libraries-cpp/

  3. tisonkun commented on Oct 25, 2022

    @tisonkun
    MemberAuthor

    @Mini256 I think in this PR #18140 we already update references of the C++/Python clients' repo. Do you spot any reference unexpected? Or do you think we should add more references at the beginning?

    Please share more details you'd like to achieve here :)

  4. Mini256 commented on Oct 25, 2022

    @Mini256

    https://pulsar.apache.org/docs/client-libraries-cpp#macos

    The first step for MacOS tells me that:

    Clone the Pulsar repository.

    $ git clone https://github.com/apache/pulsar
    ...
    $ cd pulsar-client-cpp
    $ cmake .
    $ make

    And when I execute the cmake command, I found that the code of the client has been migrated.

  5. tisonkun commented on Oct 25, 2022

    @tisonkun
    MemberAuthor

    @Mini256 Good point. In the next version, we change this section directly to the new repo's README. Let me cherry-pick to to other maintained versions.

  6. michaeljmarshall commented on Oct 28, 2022

    @michaeljmarshall
    Member

    Where should we move the python doc process? It's in the pulsar-site right now. I think we could leave the process there and just update the relevant release process docs so that the release manager knows how to generate the docs.

  7. tisonkun commented on Nov 11, 2022

    @tisonkun
    MemberAuthor

    @michaeljmarshall agree and file #18347. I'm doing this now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    doc-requiredYour PR changes impact docs and you will update later.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions