enhancements and bugfixes for version 1.17.0

[jmgrassau]

No description provided.

[github-actions]

Test Results

2 464 tests  +1   2 464 ✅ +1   19s ⏱️ ±0s
  109 suites ±0       0 💤 ±0 
  109 files   ±0       0 ❌ ±0 

Results for commit 0e41c48. ± Comparison against base commit 2ba597d.

[jmgrassau]

Hi ConjuringCoffee, ConjuringCoffee> I am curious to know why you decided to go up to version 1.17.0 instead of 1.16.3. Would you mind sharing your reasoning? I would have expected this to be 1.16.3 because the release doesn't contain any new rules or options. ConjuringCoffee> (Please note that this isn’t meant as criticism - I simply don’t have much experience with semantic versioning and would like to learn more. 😉) thanks for asking! You’re right that since there is no new feature (e. g. at least a new option somewhere), it should have been 1.16.3 from semantic versioning perspective. However, with this commit <2ba597d> that increased required versions for Java, ADT and Eclipse, both Sebastian and I felt that the change is more significant than just a patch. E. g., if someone used an Eclipse version older than 2023-06, they would need to update it to 2023-06 or later run the new ABAP cleaner version. Also, since Java 17 is now required, it somehow felt right to make this a version 1.17 😊 Kind regards, Jörg-Michael

[ConjuringCoffee]

Thanks for taking the time to explain this! I noticed the Java version change only after I submitted the comment, so I thought I could quickly delete the comment without bothering you. I didn't anticipate the e-mail notification though. 😅

[jmgrassau]

Hi ConjuringCoffee,

ah, that explains it! I had wanted to respond on GitHub, but couldn't find your comment here and wondered if there is some "send email to author" functionality that I didn't yet know of ;-) So I 'beautified' the above comment a bit now.

Kind regards,
Jörg-Michael