lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Updated] (LUCENE-4202) allow check-forbidden-apis to look for fields too
Date Mon, 09 Jul 2012 21:00:50 GMT


Uwe Schindler updated LUCENE-4202:

    Attachment: LUCENE-4202.patch

Hi Robert,
here the patch that implements this. You can add the remaining fields and commit if you like.

There is one general problem with adding deprecations in general (when doing byte-code analysis):

In bytecode, we only know two things:
- The type of field or local variable or static class, on which we do the invoke/putfield/getfield,
but we don't know any parent class.
- the name and signature of the method/field to call/getfield/putfield

So if you add java.lang.Throwable#printStackTrace() to the list, it will only find invocations
of local variables/fields of type java.lang.Throwable. So code like:

Exception e = .... / } catch (IOException e) {

will in bytecocde have no reference to java.lang.Throwable. This would need more work. I will
sleep a night about it...
> allow check-forbidden-apis to look for fields too
> -------------------------------------------------
>                 Key: LUCENE-4202
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: general/build
>            Reporter: Robert Muir
>            Assignee: Uwe Schindler
>         Attachments: LUCENE-4202.patch
> Currently this supports classes and methods, but there are some deprecated fields in
the java API, it would be nice to check for those, too.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message