refactor: Migrate from JSR 305 to JSpecify by valfirst · Pull Request #2281 · appium/java-client
Navigation Menu
{{ message }}
appium / java-client Public
- Notifications You must be signed in to change notification settings
- Fork 763
Merged
valfirst merged 1 commit intoappium:masterfrom
Mar 28, 2025Merged
refactor: Migrate from JSR 305 to JSpecify#2281
valfirst merged 1 commit intoappium:masterfrom
refactor: Migrate from JSR 305 to JSpecify#2281
valfirst merged 1 commit intoappium:masterfrom
Conversation
Copy link Copy Markdown
Collaborator
valfirst
commented
Mar 27, 2025
valfirst
commented
Change list
Migrate from JSR 305 to JSpecify.
Types of changes
What types of changes are you proposing/introducing to Java client?
- No changes in production code.
- Bugfix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
Details
Reasoning:
- https://jspecify.dev/docs/start-here/#what-is-this
- Selenium is adopting JSpecify: [🚀 Feature]: JSpecify Nullness annotations for Java SeleniumHQ/selenium#14291
valfirst
requested review from
SrinivasanTarget,
mykola-mokhnach and
saikrishna321
as code owners
mykola-mokhnach approved these changes Mar 27, 2025
asolntsev approved these changes Mar 27, 2025
valfirst
deleted the
migrate-from-jsr305-to-jspecify
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment