3rd party cert: findbugs 1.3.9 ------------------------------ Key: JBDS-1624 URL: https://issues.jboss.org/browse/JBDS-1624 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: 3rdPartyCertification Reporter: Nick Boldt Assignee: Vlado Pakan Fix For: 4.x

> All versions of LGPL (and GPL) state that if no version number is > specified, the user can use any existing version. Here it is > questionable whether > http://findbugs.sourceforge.net/manual/license.html indicates a > preference for LGPLv3 (that URL didn't always point to v3). Anyway, in > general LGPLv3 is not a 'show stopper'. And for purposes that would be > relevant here, the two licenses (LGPlv3 and LGPLv2.1) are essentially > equivalent. (Then again, the alternative licenses you've requested are > all probably preferable for various reasons if you end up having a > choice.) > > For adherence to LGPL, I would say it is enough to link to sources on > the Findbugs site (I assume you won't be modifying it further). > > I do not think LGPL/EPL compatibility issues would arise in this case.

3rd party cert: findbugs 1.3.9 ------------------------------ Key: JBDS-1624 URL: https://issues.jboss.org/browse/JBDS-1624 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: 3rdPartyCertification Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.x

3rd party cert: findbugs 1.3.9 ------------------------------ Key: JBDS-1624 URL: https://issues.jboss.org/browse/JBDS-1624 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: 3rdPartyCertification Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.x

3rd party cert: findbugs 1.3.9 ------------------------------ Key: JBDS-1624 URL: https://issues.jboss.org/browse/JBDS-1624 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: 3rdPartyCertification Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.1.0.GA