[wildfly-dev] SDDS (Silly Deployment Detector Subsystem)

Rebecca Searls rsearls at redhat.com
Wed May 29 11:37:43 EDT 2013


comment on the original post.

> 
>   I think this would be a very valuable tool.  Providing it as a CLI cmd
>   would
>   make it easist to use.  Being able to evaluate the dependencies during
>   deployment
>   would be the most helpful.  The user can run it as a deployment *lint* as
>   Scott
>   noted or as a *dry-run* before actually deploying the app.  As Steve
>   suggests
>   it should  report on the class loading env of each part of the deployment,
>   and
>   check for version issues and the like.
> 
>   Ales Justin has a utility that will help with module dependenise analysis
>   and
>   reporting  see https://github.com/alesj/moduledeps.  I've used this in
>   conjuction
>   with tattletale to identify deployed archive dependencies on AS 7 modules
>   as well
>   as missing missing classes.
> 
> 


More information about the wildfly-dev mailing list