Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions buildspecs/release-javadoc.yml
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,7 @@ phases:
- MODULES_TO_SKIP_FORMATTED=$(echo $MODULES_TO_SKIP | sed 's/,/,!:/g' | sed 's/^/!:/')
- mvn clean install javadoc:aggregate -B -Ppublic-javadoc -Dcheckstyle.skip -Dspotbugs.skip -DskipTests -Ddoclint=none -pl $MODULES_TO_SKIP_FORMATTED
- RELEASE_VERSION=`mvn -q -Dexec.executable=echo -Dexec.args='${project.version}' --non-recursive exec:exec`
- python3 ./scripts/code_examples/inject_examples.py --exampleMetadata ./codegen/src/main/resources/software/amazon/awssdk/codegen/example-meta.json --docsPath ./target/site/apidocs/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

@S-Saranya1 S-Saranya1 Dec 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, considered updating PackageInfoGeneratorTasks.java, but that approach would modify all package-info.java files for all services (70+ files). After codegen, all these generated files would contain code examples in their javadoc comments. Felt it was unnecessary to embed code examples content directly in package-info.java files, as these files should focus on package-level information rather than usage examples. Also, modifying these many files would increase the Java SDK JAR size, even though minimal. Felt post-processing approach is cleaner. WDYT?

-
- aws s3 sync target/site/apidocs/ $DOC_PATH/$RELEASE_VERSION/ --acl="public-read"
- aws s3 cp ./scripts/crosslink_redirect.html $DOC_PATH/$RELEASE_VERSION/ --acl="public-read"
Expand Down
Loading
Loading