oracle / oracle/oci-java-sdk

Published oci-java-sdk-shaded-full javadoc does not refer to shaded classes

Open
#427 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

SDK
Dominant language
Java
Stars
243
Forks
171
Avg merge
30m
Merged PRs (30d)
4

Description

See, for example, https://javadoc.io/static/com.oracle.oci.sdk/oci-java-sdk-shaded-full/2.38.0/com/oracle/bmc/http/ClientConfigurator.html#customizeBuilder-javax.ws.rs.client.ClientBuilder-

Here there is a reference to javax.ws.rs.client.ClientBuilder (the sole parameter the method declares). But the actual source code in question in the shaded artifact actually refers to shaded.com.oracle.oci.javasdk.javax.ws.rs.client.ClientBuilder (i.e. it's a shaded reference, by design).

I'm guessing the javadoc for this artifact was perhaps created before the shading process and then published with it?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the published javadoc for oci-java-sdk-shaded-full 2.38.0 with the shaded source referenced in the issue, especially ClientConfigurator.customizeBuilder. Then inspect how the artifact's javadoc is generated and published. Done means the published documentation refers to shaded.com.oracle.oci.javasdk classes rather than the unshaded javax.ws.rs types.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
documentation
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.