Make revapi report functional

[zedbeit]

The idea is to improve revapi reporting.

Some screenshots of how the report looks like now.

[metlos]

This looks ok... Could also please provide some rendered examples in the PR description so that we have a better idea about the reports?

[maxandersen]

specific reason why changing this?

[maxandersen]

i'm fine merging this - its miles better than current one :)

just that one question on chaning from error to report I wanted to understand.

[zedbeit]

The reason is for revapi to report missing classes not to fail the build

[metlos]

Note that report is the default behavior. I'm not sure why error was put in place in Quarkus config, but the effect of error is essentially an exception during the analysis, which IMHO is not that useful. report will report the missing classes as part of the analysis results so that they can be worked with in the reports.

[metlos]

One thing that I would probably try to add is the "example use-chain" that Revapi produces for the missing classes (and other differences, see reportUsesFor in https://revapi.org/revapi-java/0.27.0/configuration.html). This may be helpful for figuring out why a class is considered a part of the API by Revapi.

[zedbeit]

Thank you @metlos for your inputs.

[maxandersen]

reason for fail/error was whne running pr builds the build would not pass if missing documentation for api changes.

I thought this was the way to do so ?

[maxandersen]

@zedbeit can you rebase this then i'll merge it and we can look at example-use-chain in separate pr?

[zedbeit]

Ok done.

[zedbeit]

Added list of dependencies added/removed to the diff list.

This is how it now looks:

[zedbeit]

Added changed/updated dependencies to the diff list.

This is how it now looks:

[maxandersen]

sorry did not notice the extra commits before now. Makes a big diff on the change log. awesome.

[maxandersen]

@zedbeit can you squash the commits then we can merge it?

[zedbeit]

Made a new PR for this here, closing this one @maxandersen