Only consider existing artifacts for the classpath

[laeubi]

Currently only if the artifact file is null it is not considered but if the file does not exits JDT complains. It even seems there was once in a time such a check but it is disabled, this is an attempt to check if we can reenable it again.

[github-actions]

Test Results

  214 files  ±0    214 suites  ±0   16m 3s ⏱️ - 1m 11s
  664 tests ±0    649 ✅  -  5  10 💤 ±0   5 ❌ + 5 
1 328 runs  ±0  1 296 ✅  - 10  22 💤 ±0  10 ❌ +10 

For more details on these failures, see this check.

Results for commit 2bf3489. ± Comparison against base commit 94fa546.

♻️ This comment has been updated with latest results.

[HannesWell]

Looks like there are test-failures now. Don't know if they are only due to changed circumstances or are really meaning full.
It would be good to add a test for the case you described.

Sadly the commented out line goes back until the Initial commit at Eclipse. Would have been nice to know why this was disabled. :/

[laeubi]

@HannesWell yes thats why I have disabled it to see what / if test fails, sadly some tests are written wit some numbers of problems in the expectation without looking at the content.

At least it show it has an effect .. but probably not something for the current release.

[HannesWell]

sadly some tests are written wit some numbers of problems in the expectation without looking at the content.

Yes, that's what I meant with non meaningful tests :)
One should check each failing tests if its just the number of expected CP-entries that has to be adjusted or if the failure is really revealing a potential problem.

At least it show it has an effect .. but probably not something for the current release.

Yes, lets keep this for the next cycle.