Hello, Recently, I was thinking at a pretty nice feature that would make the grat maven tool an awesome one: code-based exclusions. Why should this be needed? Because some libs have dependencies of their own, that are not really used by the final code. In theory, one should be able to create a maven option, to exclude all the imported jars that simply aren't really used in the project. This means that maven should be able to have a plugin that parses the code, searches in depth what libraries are indeed used by this code (and what libraries are used by those libraries etc.), and what are not, and should automatically add excludes for the unused ones. The only three problems I see with this implementation right now are:- obfuscated libs;- signed libs;- libs that use reflections to load classes (like spring). Does anybody know if this should be possible?
Thanks,Bogdan Neacsu
