In Windup 1, there was the concept of blacklistedClasses that contained a list of package signatures that should be flagged if found to be used in the application being analyzed. In Windup 1, these classes just displayed the type reference, used the default "title", and were given 0 points for LOE. With the exception of a few catch-all rules, currently these packages are no longer being flagged. For now, we should add a catch-all rule for each blacklist package and use the same title and LOE from Windup 1. Two questions should be evaluated longer term:

1) Should any of these packages have a default LOE greater than 0?
2) Our rule guidance states that we should avoid 0 LOE rules as they don't seem to produce anything actionable. How do these catch-all rules fit into that guidance?

Here is the list of blacklistedClasses packages:

com.crystaldecisions
amx_
^bea
com.sonic
com.bea
com.ibm
com.iona
com.lombardi
com.tangosol
com.tibco
com.weblogic
^ilog
^commonj
java.sql.DriverManager
javax.ejb
javax.persistence
javax.management
javax.naming.Context
javax.naming.InitialContext
javax.persistence.JoinColumn
javax.sql
jrun
jrunx
mx4j
net.sf.hibernate
oracle.sql
org.apache.activeio
org.apache.activemq
org.jboss
org.mule
org.osoa
weblogic
websphere
^oracle
edu.oswego.cs.dl.util.concurrent
edu.emory.mathcs.backport.java.util
net.sf.hibernate
org.hibernate.classic.Session
org.hibernate.classic.Validatable
org.hibernate.classic.ValidationException
org.hibernate.jdbc.BatcherFactory
org.hibernate.jdbc.BatchingBatcherFactory
org.hibernate.jdbc.NonBatchingBatcherFactory
org.hibernate.jdbc.Batcher
org.hibernate.jdbc.AbstractBatcher
org.hibernate.jdbc.BatchingBatcher
org.hibernate.jdbc.NonBatchingBatcher
org.hibernate.dialect.resolver.DialectResolver
org.hibernate.connection
org.hibernate.util.EqualsHelper
org.hibernate.engine.SessionImplementor
org.jbpm