#2 output of dependentOnlyOn do not use name of subsystem

[Gero Hoffmann]

when defining a rule with dependentOnlyOn the generated output
expands the subsystem name to its containment.

for example:

[FL_BEAN_IFC] = .FLBean .FLBeanIfc
[FL_BEANS] = .FLBean excluding [FL_BEAN_IFC] com.bsp..fl.services.flberaterdatenservice.FLBeraterDatenServiceImpl
[FL_ENUM] = .FLEnum
[FL_TYPES] = java.lang.Boolean java.lang.String java.lang.Integer java.util.Date java.math.BigDecimal java.io.Serializable java.lang.Object java.util.List java.util.Map
[FL_UTILS] = .FLUtils
[VALIDATION] = .validation. .validator.*
[FL_BEAN_DEPENDENCY] = [FL_BEANS] [FL_BEAN_IFC] [FL_ENUM] [FL_TYPES] [FL_UTILS] [VALIDATION]

check [FL_BEANS] dependentOnlyOn [FL_BEAN_DEPENDENCY]

would print:

[FL_BEANS] dependentOnlyOn (.FLBean & !(.FLBean .FLBeanIfc com.bsp..fl.services.flberaterdatenservice.FLBeraterDatenServiceImpl)) .FLBean .FLBeanIfc .FLEnum java.lang.Boolean java.lang.String java.lang.Integer java.util.Date java.math.BigDecimal java.io.Serializable java.lang.Object java.util.List java.util.Map .FLUtils .validation. .validator.

which is confusing for larger list of files.

[Franz-Josef Elmer]

I've just released version 1.4.1 with improved print of the check command for dependentOnlyOn: Now it lists the unresolved set definitions.