[Clirr-devel] [ clirr-Feature Requests-1241245 ] Non-final to final method not caught
Status: Alpha
Brought to you by:
lkuehne
From: SourceForge.net <no...@so...> - 2005-08-01 07:25:56
|
Feature Requests item #1241245, was opened at 2005-07-20 01:14 Message generated for change (Comment added) made by lkuehne You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=590802&aid=1241245&group_id=89627 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Stephen Colebourne (scolebourne) Assigned to: Lars Kühne (lkuehne) Summary: Non-final to final method not caught Initial Comment: I had a method that was previously non-final. I changed the method in the new jar to be final. clirr should have produced an error but didn't. ---------------------------------------------------------------------- >Comment By: Lars Kühne (lkuehne) Date: 2005-08-01 09:25 Message: Logged In: YES user_id=401384 Fixed in CVS (and implemented the other direction as well). The detector currently always fires an error when a method changes from non-final to final. This might be wrong when the class is already final, maybe a warning would be sufficient in that case. Please file a new issue if this becomes a problem for you. ---------------------------------------------------------------------- Comment By: Stephen Colebourne (scolebourne) Date: 2005-07-20 23:32 Message: Logged In: YES user_id=408725 It may or may not be relevant, but the change ocurred on a class that is abstract. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=590802&aid=1241245&group_id=89627 |