Automatically Revealing Bloated Software Dependencies in Maven Projects

[@goldgold4943]

Superb presentation and explanation

[@cesarsotovalero]

Thanks!

[@sandulachedumitru372]

great job. Well well well done👍

[@cesarsotovalero]

Thank you! Cheers!

[@goldgold4943]

God bless you

[@andrewfedorov7914]

I used this plugin on few micro services in my company. In all cases I got a bigger jar than was before (in average on 5% bigger).

[@cesarsotovalero]

That’s strange, could you tell where the extra 5% comes from: is it from class files, resources, plugins’ metadata?

[@goldgold4943]

I am getting null pointer exception when I run this plugin

[@cesarsotovalero]

Please open an issue on GitHub and describe your problem here: github.com/castor-software/depclean/issues

[@goldgold4943]

Can you pls post the commands to generate the reduced xml.. Really hard to find online... In my office Google search is banned.. Pls help..

[@cesarsotovalero]

To get the debloated pom.xml, run the following command in your terminal:
$ mvn se.kth.castor:depclean-maven-plugin:2.0.2:depclean -DcreatePomDebloated=true