Closed JoelProminic closed 1 year ago
Done.
We'll need to test that:
Current Version | Show update in MSDKI | Update in SDK in Moonshine | Test Behavior | SDK Works |
---|---|---|---|---|
None | Yes | Yes | ||
Old version | Yes | Yes | ||
Latest version | No | No |
I confirmed that Moonshine does not automatically update to the new Grails version. It also does not automatically update to the latest Java version (#98). Did we do this intentionally so that the user could downgrade if needed for their project? I did not find a note related to this with a quick search...
We have version-update check logic available in MSDKI, but it used selectively. As I sees the logic mainly used in case of JDK8 and Flex SDK cases.
The problem from using the test globally, for every SDK, was following reasons:
software -version
in a usual manner) is problematic and tricky to parse-out a value like "xx.xx.xx" so that we can compare the value with. In About section most of the SDKs do not returns a version in simple "xx.xx.xx" but with many prefix/suffix textsIn case of Gradle, it also returns a value like Gradle x.x.x
- we can add separate handling specific to Gradle for this, but the solution may not best fit for other SDKs, though.
The SDK update issue is a bigger topic. I'm going to move this to the JDK discussion here: https://github.com/Moonshine-IDE/Moonshine-IDE/issues/1124
Gradle 7+ is required for JDK 17. We'll upgrade to the latest version, 7.5.1