You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When accessing the Javadoc websites hosted by Sonatype, the links to classes in other packages of this SDK are invalid. We need to revisit the way to generate Javadoc files to be compatible with the Sonatype's Javadoc hosting service.
Requirements (place an x in each of the [ ])
I've read and understood the Contributing guidelines and have done my best effort to follow them.
So the problem seems to be the way Maven generates links between projects- it takes the ${project.url}/apidocs as the prefix.
I'd be interested in taking a look at this one, but I can't for the life of me see how the javadocs are currently generated. I was expecting to see a attach-javadocs execution ID somewhere, but I only see the attach-source. Is there some external process that is generating the javadoc.jar? Of maybe some advanced Maven usage I'm not familiar with?
I haven't checked this issue in detail yet but the pom inherits org.sonatype.oss:oss-parent and the parent pom enables some plugins. mvn deploy command generates javadocs as part of the process.
Issue Type
Description
https://oss.sonatype.org/service/local/repositories/releases/archive/com/slack/api/slack-api-client/1.0.6/slack-api-client-1.0.6-javadoc.jar/!/com/slack/api/Slack.html#send-java.lang.String-com.slack.api.webhook.Payload-
When accessing the Javadoc websites hosted by Sonatype, the links to classes in other packages of this SDK are invalid. We need to revisit the way to generate Javadoc files to be compatible with the Sonatype's Javadoc hosting service.
Requirements (place an
x
in each of the[ ]
)The text was updated successfully, but these errors were encountered: