dev@grizzly.java.net

Re: contribution

From: charlie hunt <charlie.hunt_at_sun.com>
Date: Mon, 09 Jul 2007 09:55:53 -0500

anbaran_at_wsb-nlu.edu.pl wrote:
> Hi!
>
> I could do the following:
>
> 7) A written tutorial on how to integrate the FindBugs plug-in for
> NetBeans IDE and run it from within NetBeans IDE 5.5 / 5.5.1.
> 8) A written tutorial on how to integrate the FindBugs plug-in for
> NetBeans IDE and run it from within NetBeans IDE 6, (Note: the FindBugs
> plug-in may not operational in NetBeans IDE 6).
>
> What should it look like? Any samples, references?
>
> Cheers
> Antek
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>
>

Hi Antek,

Thanks for volunteering.

We would be happy to accept a contribution for #8, "A written tutorial
on how to integrate the FindBugs plug-in for NetBeans IDE and run it
from within NetBeans IDE 6, (Note: the FindBugs plug-in may not
operational in NetBeans IDE 6)."

You might check the comment from Sven on my blog. It appears there is
an alpha version of FindBugs for NetBeans 6.0.

We have a person who is going to contribute #7. But, thanks for
offering to contribute #7 too.

For an example of the type of document and the level of detail you can
look at https://lg3d.dev.java.net/netbeans/NetBeansLookingGlass.html.
You do not have to fancy colored sections & bars. Just a distinct font
to show different sections would be good. The most important things in
this example document are:
1.) The separation of the activities such as; download the components,
install the components and running the application, (in your case it
will be running FindBugs within NetBeans IDE).
2.) The use of screen shots to show menu items and panels within the
NetBeans IDE to illustrate which menu(s) to select, what values to use
in panels, etc.

A couple additional requirements:
1.) Could you draft it in html or pdf ?
2.) Please include pictures, diagrams and please use html link where
applicable.
3.) When you have a document ready to be reviewed, please submit a copy
of the document to this mailing list (dev_at_grizzly.java.net). Everyone
who is on the dev_at_grizzly.java.net mailing list will have an opportunity
to review your document and provide you comments.

You might consider exchanging some ideas with Torben (ttretau (at)
web.de) who is contributing #7. It would be really good if the two
documents had a similar look and flow to them.

Let me know if you have any further questions.

Again, thanks for volunteering,

charlie ...

-- 
Charlie Hunt
Java Performance Engineer
630.285.7708 x47708 (Internal)
<http://java.sun.com/docs/performance/>