[JAVA-1548] Address Clirr Report Failures Created: 13/Nov/14  Updated: 27/Nov/16  Resolved: 20/Mar/15

Status: Closed
Project: Java Driver
Component/s: API
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Trisha Gee Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: HTML File compatibility-report.html    

 Description   

The Clirr report is failing again, which means we either need to add more exceptions to clirr-exclude.yml or make sure we re-instate accidentally removed methods/classes.

The failure report is attached.



 Comments   
Comment by Jeffrey Yemin [ 20/Mar/15 ]

Since we didn't get to this on time for 3.0.0, there's not much point in doing it until 4.0. Subsequent 3.x releases should all have clean CLIRR reports against 3.0.0.

Comment by Jeffrey Yemin [ 13/Nov/14 ]

I don't agree that it provides little value, as the number of errors it reports are small enough that they can be reviewed by hand. But I would definitely like a clean report that we could fail/succeed the build on. That's going to require changes to me.trnl:clirr-gradle-plugin.

Comment by Trisha Gee [ 13/Nov/14 ]

OK - maybe we can do something a little lower-tech then. For example, add a comments section to the exclude file so that when we inspect the failures, we at least know which ones are expected failures? Otherwise the report has little value.

Comment by Jeffrey Yemin [ 13/Nov/14 ]

The CLIRR report has never passed. There are changes that have been made that CLIRR is not smart enough to recognize as being OK. For example, it reports this as an error:

Removed com.mongodb.DBRefBase from the list of superclasses

But this is safe since DBRefBase has been deprecated.

I'm not sure what to do short of rewriting CLIRR.

Generated at Thu Feb 08 08:54:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.