Ullrich Hafner

> q. Does the new `index.jelly` page require a permission check? No, I don't think that we need a permission check on any page.

Yes exactly! The problem is, that when parsing the XML there is no obvious way for me to determine which of the parent folders of `sourcefilename` are required. So I...

I hoped that https://github.com/apache/maven-surefire/pull/828 will fix this problem here as well, but this is not the case. The XML file of the nested class still has the results of all...

In https://github.com/apache/maven-surefire/issues/2601#issuecomment-3034504077 I already mentioned that I think that the expectation is wrong (with the example of #2682). Nobody commented on this comment though. Is this scenario not sufficient to...

This PR requires a lot of work as we need to ensure that existing serializations will not break. It makes sense to handle [JENKINS-61946](https://issues.jenkins.io/browse/JENKINS-61946) within the same PR as well....

> One more thing, I have exams starting on 18th November, so I’ll be able to work on this issue later this month. Please keep this PR and as well...

> Now I am ready to start working on this issue. Please review the changes so far. @uhafner It makes sense to look at the task list and the existing...

Can you check the tasks in the list? And make sure that every commit has a commit message that describes what you did in that commit! I'll have a look...

The build failures are due to the fact that the API changed. We need to bump the version to a new major release. Then the tools will be quite again.

Yes, this is a big change which needs to be carefully done, since the serialization is affected. That means need to ensure for > 20k installations that the new format...