Remove Unused Dependencies by Application in Service Center
983
Views
8
Comments
New
Service Center

The option to remove unused dependencies by eSpace is realy great! But I think it can be implemented to Applications at all. It wold be nice to have an option in ServiceCenter to remove all unused dependencies by an Application.

2014-02-07 17-02-43
Vasco Pessanha
Changed the category to
Service Center

It would be interesting to clean everything from all applications at the same time.

Nice thought. Instead of checking in all applications its better to remove unused applications via service center.

A big plus would be if this would also generate a exportable csv
With Application -> espace -> removed dependencies.


Merged this idea with 'Remove Unused Dependencies from Modules (Service Center)' (created on 24 Dec 2025 14:28:40 by Gamel)

Modules often accumulate unused dependencies after refactoring or feature removal, which increases technical debt and complicates maintenance. I suggest adding an option in Service Center to detect and safely remove unused dependencies from modules, with basic impact analysis to avoid breaking changes. This would help keep applications clean, improve maintainability, and reduce architectural complexity.

I like this. 

I would suggest removing unused dependencies during deployment, but keep them in the code model (used in ServiceStudio). 

This would mean:

  • deployed code is cleaner
  • if needed, you can still use the unused dependency and deploy, where only then it is actually deployed in the code.

Reasoning:

For the underlying removal during deploy:

Often we clean up unused dependecies. i.e. on module level, remove unused (Love this feature!)

But, it means you need to add the dependencies again each time you want to continue building.


For maintaining in code model:

if a hot fix is needed (some still do, I really dislike it) the dependency is available.


I would do the same for unused code (actions,...)


kind regards,

Wouter

Thanks a lot, Wouter — that’s a really good point 👍

I actually like the idea of separating code model cleanliness from deployed artifact cleanliness. Keeping unused dependencies in Service Studio while excluding them from the deployed code sounds like a very balanced approach.

This would give us:

  • Cleaner and smaller deployed artifacts

  • Zero friction during development (no need to re-add dependencies repeatedly)

  • Safer hotfix scenarios where the dependency is already available if urgently needed


Really appreciate the feedback — it adds a lot of practical value to the original idea.