I think I would tackle this with a series of shell scripts (if we're dealing with linux). I would use some permutation of
find . -type f -print0 | xargs -0 wc -l | sort -n; to list files by line length. There are several scripts available to check circular dependencies in source trees and I would piggy back that on the line check. On Tuesday, February 7, 2017 at 8:51:59 PM UTC-7, Yanwei CHANG wrote: > Hi plugin developers, > > Hope you are doing well. > > I am a developer and recently I am facing with a requirement that needs to > scan bunch of source codes to find out what design problems potentially > exist. > > Specifically, as for now I just need to implement several simple rules, > like the packages should not being circular dependent, the file should not > be big, like less than 2000+ lines, something like that. But in the future > more complex rules will be added. Also I need to generate a XML report that > align with some specific format. > > By the way, I was talking about Java, but also I need to support C/C++ > just for now. > > I am currently searching for some plugins that I can work based on that to > extend my own requirements easily, like more customised rules. Also I think > integrated with other plugins should be a good idea, like work with Doxygen > plugin or other plugins. But I am not sure if it is a valid point from > technical perspective. > > I will highly appreciate if you can suggest some plugins, or some > materials that can provide direct help for my upcoming development work. > > Thanks sincerely, > > Yanwei > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2b880e98-2916-40ab-a75d-39623cfa1888%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
