Need ability to add very specific exceptions

[keith-turner]

While analyzing Accumulo's API I have run into some mistakes made in the past. For example AbstractInputFormat has a method called getTabletLocator() that returns a non public API type. I would like to add a very specific exception to ignore this method.

[ctubbsii]

One simple way to add an exception currently is to mark the mistake with @ Deprecated . Is there a use case for ignoring specific non-deprecated problems?

[keith-turner]

One simple way to add an exception currently is to mark the mistake with @ Deprecated .

If its an existing problem that one does not have the time to deal with (like deprecate and provide a replacement), its nice to have the option to ignore it.

[ctubbsii]

One possible concern: learning the syntax for exceptions may be more burdensome than deprecating, in many cases, and will likely not be very frequently used. As such, the potential extra complexity to add to the plugin may not be worth it if people aren't going to use it.

Another use case: if you actually want to analyze deprecated code (for whatever reason) and need a different way to declare an exception.

[keith-turner]

I changed the milestone to 1.1.0 because I think this important for initial adoption. Users can start using the plugin, ignoring existing problems. In this scenario users can get the benefit of preventing new problems in the API immediately.

[keith-turner]

Could offer a specific annotation that instructs Apilyzer to ignore problems in a method or class.