remove old jars from deployment when deploying new version of module

Hi All,

When I deploy a new version of a module the resources of the previous module remain undeleted in the deploy lib directory.

So if I switch from my-support-1.0.jar to my-support-1.1.jar then both libraries end up in the deploy directory.

When I do a deploy can all resources of the previous module be removed ?

(unless they're also being used by another resource, in which case we're in trouble)

Maybe OSGi is a way forward for the module system?

That allows for bundles with each their own classpath resources.

regards,

                       Paul

1 Comment
kohlbrecher
Crownpeak employee
Crownpeak employee

Hi Paul,

I created an internal ticket for this (internal ID CORE-8302). It is classified as a bug.

You can find more details about our feature selection process in our Features Policy.

Best regards

Jan