Hello Seema,
Welcome.
I have documented some enhancement requests in issue tracker [1] (choose
sub-category as verifier to get the list). Since you are familiar with
ASM and other byte code engineering libraries, I think issue 3625 [2]
would be an excellent starting point.
On a longer term:
The next big feature planned for verifier is support for Java EE 6 [3].
But, before we add support for Java EE 6, I think we should address some
of the infrastructural issues in verifier that stops it from used in an
IDE environment. Your background fits very well for the areas of
improvement in verifier. I will drop another email providing some more
background. I am trying to find out if we can have a separate mailing
list (like verifier_at_glassfish.dev.java.net) to discuss about verifier.
Until then, let's use this mailing list to communicate.
Thanks,
Sahoo
[1]
https://glassfish.dev.java.net/issues/query.cgi
[2]
https://glassfish.dev.java.net/issues/show_bug.cgi?id=3625
[3]
https://glassfish.dev.java.net/issues/show_bug.cgi?id=4148
Seema Richard wrote:
>
> Hello,
>
> I’m working with an IT services company in Trivandrum, India. A few of
> my colleagues and I have been looking at the Glassfish verifier source
> code and found it interesting. To know more about how we can
> contribute to the verifier, we contacted Sahoo who is leading this
> module at Sun. He advised us to join this mailing list.
>
> We have been playing around with the different APIs for binary /
> source code analysis such as ASM, Compiler Tree API and the Pluggable
> Annotation Processing API. Please send us your inputs on how we can go
> about contributing to the Glassfish verifier project. We have already
> faxed across the SCA (Sun Contributor Agreement).
>
> Thanks,
>
> Seema
>