aboutsummaryrefslogtreecommitdiff
path: root/devel/java-findbugs
Commit message (Collapse)AuthorAgeFilesLines
* Remove NOPORTDOCS and NOPORTEXAMPLES.Adam Weinberger2014-07-031-8/+2
| | | | | | | Approved by: portmgr (blanket) Notes: svn path=/head/; revision=360487
* . Use a valid JAVA_VERSION specification.Greg Lewis2014-06-101-1/+1
| | | | Notes: svn path=/head/; revision=357271
* . Support staging.Greg Lewis2014-06-101-12/+11
| | | | Notes: svn path=/head/; revision=357270
* Add NO_STAGE all over the place in preparation for the staging support (cat: ↵Baptiste Daroussin2013-09-201-5/+2
| | | | | | | devel part 2) Notes: svn path=/head/; revision=327723
* . Add missing PLIST_DIRS entries.Greg Lewis2011-03-151-0/+3
| | | | | | | Pointed out by: ale@ Notes: svn path=/head/; revision=270940
* . Add a port of FindBugs:Greg Lewis2011-03-134-0/+169
FindBugs looks for bugs in Java programs. It is based on the concept of bug patterns. A bug pattern is a code idiom that is often an error. Bug patterns arise for a variety of reasons: * Difficult language features * Misunderstood API methods * Misunderstood invariants when code is modified during maintenance * Garden variety mistakes: typos, use of the wrong boolean operator FindBugs uses static analysis to inspect Java bytecode for occurrences of bug patterns. WWW: http://findbugs.sourceforge.net/ Notes: svn path=/head/; revision=270825