Auto-remove empty packages from Export-Package when all classes are deleted

[nburnwal09]

When all Java classes within a package are deleted through refactoring operations, the package remains listed in the Export-Package header of the MANIFEST.MF (if already added). This creates an inconsistency where the plugin exports a package that no longer exists or is empty, which can lead to invalid OSGi bundle metadata, build warnings or errors, potential runtime issues for consumers of the exported package

Expected Behavior:
When all classes in a package are deleted via delete operation, the package(having no java files or any other resources) should be automatically removed from the Export-Package header in MANIFEST.MF if it was previously exported.

deletion.refactor.mp4

[nburnwal09]

I am working on it

[merks]

I thought I'd mentioned it; you mention all classes but I assume you are also consider account other things like resources.

[nburnwal09]

I thought I'd mentioned it; you mention all classes but I assume you are also consider account other things like resources.

Yeah you are right. I didn’t account for other resources; I’ll update the issue to include that.