You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JDiff doesn't figure out the difference because of the generic types of Flux and Mono arguments, and gives them the type <any> which ends up with a duplicate error and Jdiff does not create the report...
Logs:
[ant:Comparing versions] JDiff: reading the new API in from file '[...]/spring-framework/build/reports/jdiff/5.2.0.M1_to_5.2.0.BUILD-SNAPSHOT/Spring_Framework_5.2.0.BUILD-SNAPSHOT.xml'...Error: duplicate comment id: org.springframework.transaction.reactive.TransactionalOperator.transactional_changed(<any>)
> Task :jdiff
Report location: [...]/spring-framework/build/reports/jdiff/5.2.0.M1_to_5.2.0.BUILD-SNAPSHOT/changes.html
As a workaround, you can (before generation) remove the generic types for Mono and Flux in both org.springframework.transaction.reactive.TransactionalOperator#transactional(Flux) and, org.springframework.transaction.reactive.TransactionalOperator#transactional(Mono). Then rollback the change after the generation.
I'm working on refactoring our Gradle build in #23282; in the process, I'm testing Japicmp.
The output format is not the same but at least it seems maintained and we wouldn't have to store binaries in our repo anymore...
I'll sync up with @snicoll to check whether the new output format works out for our needs.
Our release process includes a command to run to be able to generate the binary diff between two releases.
First step is to get a repo with the previous release, e.g.
Then, from the repo at the target (about to release version) we can run the following:
This generates a report with the diff (here's an example for 5.1). Running that command on
master
does not generate thechanges.html
file anymore.The text was updated successfully, but these errors were encountered: