By comparison with:

    (cd $JBOSS_HOME/modules/system/layers/base; find . -name module.xml -exec grep -q 'property.*name.*jboss.api' '{}' \; -print|xargs egrep -h '(module.*xmlns.*name=|jboss.api)' ) | less


I found the following modules listed as non-public (a few were already in this file, but shouldn't have been):

	./org/antlr/main/module.xml [already here]
	./org/apache/commons/collections/main/module.xml
	./org/apache/commons/codec/main/module.xml
	./org/apache/commons/lang/main/module.xml
	./org/apache/james/mime4j/main/module.xml
	./org/apache/httpcomponents/main/module.xml
	./org/codehaus/jackson/jackson-core-asl/main/module.xml
	./org/codehaus/jackson/jackson-mapper-asl/main/module.xml
	./org/dom4j/main/module.xml [already here]
	./org/javassist/main/module.xml
	./org/slf4j/impl/main/module.xml [already here]
	./org/yaml/snakeyaml/main/module.xml
	./org/scannotation/scannotation/main/module.xml
	./com/h2database/h2/main/module.xml [already here]

We should remove the module references from this file if we can, *but* we may not need to deploy all of them as jars inside zanata.war.  I think we only need to include the jar if we use it from Zanata code (ie a `compile` scope dependency).  If the private jboss module is only used by one of the public jboss modules, we might be able to remove the Maven dependency entirely, the private module should be pulled in automatically by the public module (without a reference here), and that should be okay.

Also, we should sort the module names in this file.