The project I am working on has dependencies on some of the most famous and large libraries. Things are working well, so far the sensory dependencies are playing well with each other. But unfortunately, the total bundle size is around 100 MHz.
I'm not sure whether this is too big or not, but is there a way to effectively remove pom.xml with very verb and long-lasting dependency effectively?
And the indicators will be horrible to help me in the right direction!
You can remove dependencies by declaring exclusions which I first post the question. Why do you want to delete them?
Unless you know that dependence is not needed, it may be that they do not try to remove them. Especially if there are no problems in case of application performance or startup time
Maven dependency plugins as well as Eclipse integration tools that allow you to understand better reliance with dependency tools such as: tree Target or POM Dependency Hierarchy View
Do not try to fix something that is not broken.
But if you really know what is required on runtime and using tooling from Maven and M2E, then perhaps you should remove lots of your final artwork though you can use it by using Dependent Exclusions You have to configure in. The new Maven versions also allow patterns to be used.
One more thing you can do is to use a device like Progu, which removes all unused classes from the final artifacts. It can be quite complex but can also be very effective
It will depend on you to find the right balance between the effort and effort of the effort.
No comments:
Post a Comment