[KIEKER-2000] Fix eclipse build problems

[rju]

JIRA Issue: https://kieker-monitoring.atlassian.net/browse/KIEKER-2000 Original Reporter: DaGeRe

---

When we import Kieker into eclipse, there are again problems with building the project:

• With 48be0261cf4edb247fc736d5c4cd2801e87cb0a9, everything works fine using eclipse 2023-06 (4.28.0)
• With 04c7bcb4c249329313725f0b83a502ed1b213c60, javax.xml.namespace.QName cannot be found in analysis → src-gen (but everything else works fine using eclipse 2023-06 (4.28.0)
• With ce6c7b7b38aaac6bc58310a94c339b4c79fdb51d (current main), teetime.framework.test.StageTester and everything else from {{testImplementation "de.cau.cs.se.teetime:teetime:$ {libTeetimeVersion}

  :test"}} cannot be found; setting the version explicitely to 3.1.1 doesn’t solve the problem

As pointed out by oleosterhagen in https://github.com/eclipse/buildship/issues/1266#issuecomment-2297138252 , it seems like we can remove the eclipse classpath specification that was added in 46193446752a40715e5626c0c478145384a35ccd, but this does’t fix the problems with other imports.

Checklist:

JIRA Comments:

557058:62e50ed6-5f61-4540-a49c-a43b84d72ea5 (JIRA username) added a comment on Fri, 13 Sep 2024 17:03:27

One problem might be that we use javax.xml.bind:jaxb-api:2.3.1, but this should be replaced by jakarta.xml.bind-api (https://mvnrepository.com/artifact/javax.xml.bind/jaxb-api ) But to do so, we’d need to update the code that generates the classes.

[rju]

author DaGeRe -- Fri, 13 Sep 2024 17:03:27 +0200

One problem might be that we use javax.xml.bind:jaxb-api:2.3.1, but this should be replaced by jakarta.xml.bind-api (https://mvnrepository.com/artifact/javax.xml.bind/jaxb-api ) But to do so, we’d need to update the code that generates the classes.