> Usually the major sticking point for our use of LGPL is if we have to
> import code (i.e. import com.* statements). Since neither of the
> findbugs plugins do this, I'd wager that it being lgpl isn't an issue.
> If it is, then we're going to have to take yet another look at plugins -
> chec
Ben Walding <[EMAIL PROTECTED]> wrote on 01/09/2003 07:31:00 AM:
> I missed discussion of the previous version unfortunately. And it isn't
> listed on the main page at the maven-plugins.sf.net site - only in CVS.
>
>
> Usually the major sticking point for our use of LGPL is if we have to
> i
maven core to increase usage.
Eric Pugh
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 30, 2003 1:15 AM
To: [EMAIL PROTECTED]
Subject: cvs commit: maven/src/plugins-build/findbugs plugin.jelly
bwalding2003/08/29 16:15:15
Modified:src/plugin
> Subject: cvs commit: maven/src/plugins-build/findbugs plugin.jelly
>
>
> bwalding2003/08/29 16:15:15
>
> Modified:src/plugins-build/findbugs plugin.jelly
> Log:
> Was using incorrect sourcepath variable
>
> Revision ChangesPath
> 1.2 +
bwalding2003/08/29 16:15:15
Modified:src/plugins-build/findbugs plugin.jelly
Log:
Was using incorrect sourcepath variable
Revision ChangesPath
1.2 +4 -4 maven/src/plugins-build/findbugs/plugin.jelly
Index: plugin.jelly
===
bwalding2003/08/28 18:55:48
Added: src/plugins-build/findbugs plugin.jelly maven.xml
project.properties project.xml plugin.properties
Log:
First cut of a findbugs plugin. For the time being
* Won't create a report
* Will generate text output in your mav
