On Jul 27, 2011, at 4:04 PM, Bill Shannon wrote:
> Tim Quinn wrote on 07/27/11 12:24 PM:
>>
>> On Jul 27, 2011, at 2:19 PM, Bill Shannon wrote:
>>
>>> Tim Quinn wrote on 07/27/11 11:41 AM:
>>>>
>>>> On Jul 27, 2011, at 1:12 PM, Byron Nevins wrote:
>>>>
>>>>> KUDOS to whomever invented and implemented this idea. I almost
>>>>> always forget
>>>>> to update the copyright year. ..
>>>>
>>>> Indeed.
>>>>
>>>> Now, if this technology can be built into a maven plug-in that's
>>>> run
>>>> automatically as part of our builds in our own workspaces, so we
>>>> can find out
>>>> BEFORE we check in the offending files...
>>>
>>> Where's that "Beginner's Guide to Writing Maven Plugins"? :-)
>>>
>>> What's an existing (simple) maven plugin that does something
>>> similar,
>>> i.e., analyzes all the source code in a project?
>>
>> I don't know how simple the FindBugs one is, but that certainly looks
>> at all (Java) source code.
>
> No, it reads class files.
I should have known that.
>
> And it's somewhat of a cheat - the maven plugin just constructs the
> command line to call the external FindBugs program.
Where's the fun in that?!
- Tim