Details
-
User Story
-
Resolution: Fixed
-
P2: Important
-
6.8
-
None
-
-
2024wk24s2FOQtforAndroid, 2024wk26s2FOQtforAndroid, 2024wk38s2FOQtforAndroid, 2024wk28s2FOQtforAndroid, 2024wk30s2FOQtforAndroid, 2024wk32s2FOQtforAndroid, 2024wk36s2FOQtforAndroid, 2024wk40s3FOQtforAndroid, 2024wk42s3FOQtforAndroid
-
21e2b9e94 (dev)
Description
Following C++ API review rounds, and because of the QML embedding into native Android apps, the Java APIs, will be more exposed to users. Thus, to keep changes in check, do steps to start a formal API review round for Java.
This would ideally mean having a script(s) that makes the process automated, that would eventually live under qtqa/scripts/api-review.
I've looked into javap and javadoc tools for generating public API changes that can then be used to generate a diff. javadoc seems more promising because it would include the actual docs changes and not only the high level declarations that's generated with javap. Using javadoc Doclet API it might be possible to create a custom format like Markdown instead of the default HTML format.