RFR: 7903964: Fix NPE in JTRegConfiguration.getJDKString [v2]

[duke]

On Fri, 7 Mar 2025 16:51:27 GMT, Oleksii Sylichenko <duke at openjdk.org> wrote:

>> # This bug appears when
>> - The user removes the "Build" target from "Before launch" in the Run Configuration.
>> - The user unsets or does not set the Project SDK, or if it has been removed from the file system.
>> 
>> # Steps to reproduce
>> 
>> 1. Open a JDK project.
>> 2. Open "Project Structure".
>> 3. Select an SDK in the Project tab.
>> 4. Navigate to "Settings → jtreg".
>> 5. Set "JRE = "Default".
>> 6. Run a test to automatically create a run configuration, or manually create one with "JRE = Default".
>> 7. Open Project Structure again.
>> 8. Set SDK = "<No SDK>".
>> 9. Edit the previously created Run Configuration and remove the "Build" target from "Before launch".
>> 10. Run the previously created Run Configuration.
>> 
>> ## Expected
>> - Error message appeared: "No valid JDK configured for running jtreg tests"
>> 
>> ## Actual:
>> - Nothing happened
>> 
>> # Implemented Changes
>> 
>> ## JTRegConfiguration.java
>> - Add the `@NotNull` annotation to methods that are missing it but have it in the parent method.
>> - Add javadoc to `getJDKString`.
>> - Refactor `getJDKString`:
>>   - Fix method getJDKString, to prevent NPE when Default SDK for the project was not set
>> 
>> ## JTRegConfigurationRunnableState.java
>> - Change visibility to `public` to eliminate the warning in `JTRegConfiguration#getState`.
>
> Oleksii Sylichenko has updated the pull request incrementally with one additional commit since the last revision:
> 
>   7903964: Fix NPE in JTRegConfiguration.getJDKString
>   - remove `final` from local variables

@asilichenko 
Your change (at version c0ade71360d8a59eb5e7be74895b5ddb94c4b605) is now ready to be sponsored by a Committer.

-------------

PR Comment: https://git.openjdk.org/jtreg/pull/251#issuecomment-2707029888