| Re: [pde-dev] "Find unused dependenceis" from command line? |
Hi Tom.
It would be great to automate the tasks as you described but that would be difficult to make it work in general.
Most OSGi development is done on top of some kind of dependency injection framework (DS, Spring DM / Gemini). If you automate the process to remove the unused dependencies, you will come across the case that you have removed a dependency that was declared in one of the DI configuration file.
Regards,
Christian
To: pde-dev@xxxxxxxxxxx
Subject: [pde-dev] "Find unused dependenceis" from command line?
Hi List,
I hope I am talking up the right list, if not, maybe someone can point me to the right list.
I would like to call the "Find unused dependencies" functionality of the "Plug-in Manifest Editor" from the command line. Does anybody know if and how?
We have about 50 projects and 10 developers. Experience has proven that the developers will not think of erasing unused dependencies in the heat of the battle. Going through all manifest files and erasing the unused dependencies is a tedious job I would happily like our CI build machine to do. Hence my question.
I am also curious why this is not the default thing during a build. What is the use of pulling in stuff that will never be used? I could imagine removing unused dependencies before packaging and maybe a flag if you realy-realy want unused stuff in the resulting plugin. That would be a lot handier, right? But this is a bit besides the point of my question above.
Thanks,
Tom
Le contenu de ce courriel s'adresse au destinataire seulement. Il contient de l'information pouvant être confidentielle. Vous ne devez ni le copier ni l'utiliser ni le divulguer à qui que ce soit à moins que vous soyez le destinataire ou une personne désignée autorisée. Si vous le receviez par erreur, veuillez nous aviser immédiatement et le détruire.