Open smeubank opened 1 year ago
Assigning to @getsentry/support for routing, due by (sfo). ⏲️
List of potentially relevant files https://github.com/getsentry/sentry-docs/pull/7086/files
Routing to @getsentry/product-owners-sdks-web-backend for triage, due by (vie). ⏲️
@smeubank @adinauer is this fixed by https://github.com/getsentry/sentry-docs/pull/7086?
@kahest no, this is a follow up to improve docs.
Core or SDK?
Platform/SDK
Which part? Which one?
Java (including Kotlin and Android)
Description
The Java (and related platforms) documentation for configuring an application to create releases and upload source context, includes a lot of variation and is rather verbose. It may not be simple for users to navigate and find the specific configurations which are needed for their application, while being confused with all the different variations of Java and build tools in one page #
Suggested Solution
Is source context industry standard terminology in Java? Can we just say source code or something?
To start we would like to make the structure of the Java documentation for source context follow the same format as JavaScripts source map's docs
There is a dedicated page for Gradle, but it is not clear to me why that is there and not maven, it also seems to contain content about source context which is duplicated. Instead under source context we could have single dedicated pages for Maven and Gradle
There are product docs (CLI -> Debug Information Files) which include information about uploading source context for Java, this belongs in platform documentation. So as to not duplicate and confuse users reading generic product docs to see things about any specific platform in detail