isExpectedFolder(): log level now generic with default being WARNING

[ssmid]

Fixes #818

[CLAassistant]

All committers have signed the CLA.

[coveralls]

Pull Request Test Coverage Report for Build 13859769305

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 141 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+0.002%) to 67.659%

---

Files with Coverage Reduction	New Missed Lines	%
com/devonfw/tools/ide/tool/ide/IdeToolCommandlet.java	5	77.59%
com/devonfw/tools/ide/io/FileAccessImpl.java	136	68.43%

Totals
Change from base Build 13859584846:	0.002%
Covered Lines:	7826
Relevant Lines:	11139

---

💛 - Coveralls

[julia-cap]

The changes look good to me.

• I tested the PR locally in a new project workspace by using the github cli gh pr checkout 1118. After running ide intellij no error message appeared
• All tests passed locally
• Maven build runs successfully
  Review done without any further comments.

[julia-cap]

@ssmid Andre, please update your feature branch. I do not have permission to do so for your PR, it seems.

[hohwille]

@ssmid thanks for your PR. You even followed the trace from my comment and tried to implement this properly. 👍
However, I have to crush the party here.
I was confused why the error message should be fixed by this PR as this did not make sense to me.
Then I tried to reproduce the issue and figured out that it cannot be reproduced any-more with or without this PR.
I tried to find an explanation for this and found it in our git history...

This is the "old" code that was previously causing the problem:

IDEasy/cli/src/main/java/com/devonfw/tools/ide/tool/ide/IdeToolCommandlet.java

Line 74 in 12cdd64

if (!fileAccess.isExpectedFolder(setupFolder) && !fileAccess.isExpectedFolder(updateFolder)) {

However, the bug #818 was already fixed some time ago but most probably as a side-effect of some other bugfix or feature (most probably #982).
So if there is no bug we also do not need a bugfix.
I hope not to frustrate anybody involved here and hope you take it as a learning to always first reproduce the issue before fixing it.